mikeydk

Members
  • Posts

    68
  • Joined

  • Last visited

Posts posted by mikeydk

  1. 3 minutes ago, JorgeB said:

    More likely to get a reply in the existing container support thread/discord, assuming one exists:

     

    docker support.JPG

     

    I tried the support thread too, waited 5-6 days with no reply, deleted the message again to not post same message multiple places.

  2. Has anyone tried to restore a database in the influxdb docker?

     

    I got the database exported from another source in the portable format, and looking at restoring it.

     

    I have found this https://www.influxdata.com/blog/backuprestore-of-influxdb-fromto-docker-containers/ but I don't know how to actually execute the procedure with unraid.

  3. 3 hours ago, JorgeB said:

    This workaround doesn't always work, but also note that if you're using AMD hardware it's different.

    Ah, I didn't see there were two different ones. I am on AMD, sadly it didn't work changing it. I got it to work by setting it to off, and right now that isn't a problem, but I have some plans on the future where I need it enabled. Is the solution then to get another card? 

  4. On 6/15/2015 at 10:50 PM, RobJ said:

    Update:  A potential workaround - some users are reporting success with the following workaround, add iommu=pt to the append line of your syslinux.conf file on your boot flash.

      Example - change this

          append  initrd=/bzroot

      To this

          append  iommu=pt  initrd=/bzroot

    I have tried to add this, as I don't see the disk attached to the card in unraid.

    Inside the card's bios I do see the disk.

     

    In syslog I got this

    Nov 14 15:36:41 Selina kernel: ahci 0000:09:00.0: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x000000000009d200 flags=0x0000]

    followed by this a bit further down

    Nov 14 15:36:41 Selina kernel: sd 6:0:0:0: [sde] Attached SCSI disk
    Nov 14 15:36:41 Selina kernel: ata9: link is slow to respond, please be patient (ready=0)
    Nov 14 15:36:41 Selina kernel: ata16.00: qc timeout (cmd 0xa1)
    Nov 14 15:36:41 Selina kernel: ata16.00: failed to IDENTIFY (I/O error, err_mask=0x4)
    Nov 14 15:36:41 Selina kernel: ata16: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
    Nov 14 15:36:41 Selina kernel: ata9: COMRESET failed (errno=-16)
    Nov 14 15:36:41 Selina kernel: ata9: link is slow to respond, please be patient (ready=0)
    Nov 14 15:36:41 Selina kernel: ata16.00: qc timeout (cmd 0xa1)
    Nov 14 15:36:41 Selina kernel: ata16.00: failed to IDENTIFY (I/O error, err_mask=0x4)
    Nov 14 15:36:41 Selina kernel: ata16: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
    Nov 14 15:36:41 Selina kernel: ata9: COMRESET failed (errno=-16)
    Nov 14 15:36:41 Selina kernel: ata9: link is slow to respond, please be patient (ready=0)
    Nov 14 15:36:41 Selina kernel: ata16.00: qc timeout (cmd 0xa1)
    Nov 14 15:36:41 Selina kernel: ata16.00: failed to IDENTIFY (I/O error, err_mask=0x4)
    Nov 14 15:36:41 Selina kernel: ata16: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
    Nov 14 15:36:41 Selina kernel: ata9: COMRESET failed (errno=-16)
    Nov 14 15:36:41 Selina kernel: ata9: limiting SATA link speed to 3.0 Gbps
    Nov 14 15:36:41 Selina kernel: ata9: COMRESET failed (errno=-16)
    Nov 14 15:36:41 Selina kernel: ata9: reset failed, giving up

    So if I read this correct there is 3 timeouts on a 4 port card, which seems logical, as I only got one disk connected to it.

     

    In System Devices I got this under "IOMMU group 18"

    	[1b4b:9230] 09:00.0 SATA controller: Marvell Technology Group Ltd. 88SE9230 PCIe SATA 6Gb/s Controller (rev 11)

    Do I need to do something else to get unraid to see the drive, or should it just be there as the drives attached to the mainboard?

  5. 2 minutes ago, ich777 said:

    Please update the container, I've now made a quick fix where it stays on version 4.1.0 and should cause no problems anymore.

    Will update the container in the next few days to work properly if that's ok for you. ;)

    Thank you, got it to start up now, so the quick fix worked. :)

    • Like 1
  6. Trying to use the TheLounge docker, but the log is showing this, and the gui can't be reached.

     

    ---Checking if UID: 99 matches user---
    ---Checking if GID: 100 matches user---
    ---Setting umask to 000---
    ---Checking for optional scripts---
    ---No optional script found, continuing---
    ---Starting...---
    ---Version Check---
    
    ---Version missmatch, installed v4.1.0, downloading and installing latest v4.2.0...---
    
    ---Something went wrong, can't download TheLounge v4.2.0, putting container into sleep mode!---

     

  7. I have added a secondary cache disk, and I am running the cache pool in raid 1.

     

    After adding that Fix Common Problems is now reporting an error

     

    The following files exist within the same folder on more than one disk.  This duplicated file means that only the version on the lowest numbered disk will be readable, and the others are only going to confuse unRaid and take up excess space:
    
    /mnt/user/system/docker/docker.img   disk2 cache
    /mnt/user/system/libvirt/libvirt.img   disk2 cache

    Is that something I can just ignore? With raid 1 all the files should exist on both drives at the same time?

  8. Just tried to install this, but it cant start, getting this in log

     

    �[36mINFO�[0m[0000] Starting Statping v0.80.71 �[36mtype�[0m=cmd
    
    New Update 0.80.70 Available!
    Update Command:
    curl -o- -L https://statping.com/install.sh | bash
    
    �[31mERRO�[0m[0000] config.yml file not found at /app/config.yml - starting in setup mode �[31mtype�[0m=cmd
    �[31mFATA�[0m[0000] user doesn't have permission to write to this directory �[31mtype�[0m=cmd

    Do I manually need to put a config.yml file in? If so, where do I find it?

  9. I got it working.

     

    To get it to work I had to change Network Type to Bridge, and then add a port.

     

    After doing this the WebUI option no longer direct to the right address, but typing the address in manually works.

     

     

    Scrap that... F5 and it is back to the 3 dots again.

  10. I am having some problems getting this to run.

    I took the filebrowser.json and put it in

    /mnt/user/appdata/filebrowser/filebrowser.json

    But when I start the docker and tries to access the webui, I just get 3 dots fading from left to right.

    Log file contain this

    2020/01/12 16:35:14 Using config file: /.filebrowser.json
    2020/01/12 16:35:14 Listening on [::]:80

    No matter what port I set in the json file, it continue to listen to port 80 too.

     

    Opening console I am getting a fast flash of an error containing something with $PATH. It is flashing so fast I can't read it.

  11. On 8/2/2019 at 9:03 AM, ich777 said:
    On 7/20/2019 at 10:51 AM, QuantumMechanic said:

    I have a question about OpenTTD - what do I need to do to make the server load the last autosave when the server restarts? I can't find any documentation for this. Thanks.

    Oh, doesn't it load the last savegame? Maybe @mikeydk can help?

    When you go in and edit the docker, you got the option to set extra start parameters, there you just add 

    -D -g "<full path to save game>"

    You can find it and more on this page https://wiki.openttd.org/Dedicated_server

  12. Seems to be something up with the pluginUdklip.thumb.PNG.c6860033dc98f8b53d813a1ae5565fbf.PNG

     

    46 minutes ago, strike said:

    But to me, it seemed like the only way you got it to work was when you used the root user (which is the way it's supposed to work) and when you tried to put in another user it didn't work because it still used root (?).

    I actually think it all started with a bad ui design. There is a field for ip, port, username and password. But as it seems, username and password are not related to each other. You can change the username to whatever you want, but the password must be for the root user on the server. But nothing is explaining how that is, and nothing is put in to indicate they are not connected. What has been confusing on top, is that I have apparently tried to use it as intended, but since I am not sharing passwords across multiple users, I could not get it to add the server to the list, because it was the wrong root password. The app isn't showing any error messages, it just silently goes back to the server list, where nothing is added, no matter what the problem is.

    I only just now found a place in the faq where it mention the need of root password, and that is only because I was looking specifictly for that. I have even been on it before, but there were two topics about connecting, then it continued to the plugin. It turns out, after that, it goes back to explain about connecting.

     

    So I probably misunderstood how to use this. And failed to find the documentation needed, but I got some suggestions to make this easier to find and use.

     

    FAQ

    Move the "I’m having issues accessing the app with any user other than root" section up to the other relating connecting.

    Move "Can you add x, y, z feature ?" down to "I’m having x, y, z issue with the app", as they are both related to something else not covered.

     

    Mobile app

    Split it up, so it is clear to see what part is related to the connection to the server, and what part is related to the user to use.

    In the server part there could be, as there is now, a field for ip, port, username where it is set to root and disabled so it cant be changed, followed by password, server name, and the secure toggle.

    After that a wider line or something to split the interface up, and then have a field for the user.

    Also adding some error messages to the mobile app would be very helpful, then users wouldn't have to guess why nothing happened.

  13. Just now, strike said:

    I don't think this app supports what you're trying to do. 

    I dont think so either, now. But it is actually the only thing I can get to work.

    If I put unraid's ip and port 443 in, I get the dash and access to start and stop all dockers, which work just fine. But to do that, I need to create a root user the app can log in with (because the username field is for the plugin, but the password field isnt?).

     

    I have also tried to put the ip of unraid in, but then start the server from the plugin and put the port in it it is showing, but when I press ADD in the app, I am just send back to the server list, without getting anything added, and then I can go back and try to put everything in again, and just have it all erased and send back to the empty server list.

     

    Trying to access the UI in the plugin shows this too

    Quote

    Unable to connect to serverx

    (1001) - Unable to get unRAID state (dockers): Get https://127.0.0.1/plugins/dynamix.docker.manager/include/DockerContainers.php: dial tcp 127.0.0.1:443: connect: connection refused

     

    So the only way I can get it to work, is the way it isn't supposed to work. But it is actually working pretty well that way, except the username field is being used for something else.

  14. 9 minutes ago, strike said:

    You say that nginx runs as root

    I dont think I ever said that.

     

    2 minutes ago, strike said:

    How exactly do you tell nginx what user to log into unraid with?

    proxy_set_header Authorization

     

    With this you can make nginx do the basic auth unraid is using, while having another login when accessing nginx. And it actually seems to work pretty well. When trying to access unaid, you go to a link, and the basic auth is popping up, but instead of getting the one from unraid, it is the one from nginx. This allow me to block brute force attacks, along with a bunch of other things.

     

    7 minutes ago, strike said:

    So essentially you have to log in twice, once with whatever user you set up in the htpasswd file, and once with the REAL username and password to the service. 

    No, I only log in once, nginx is then applying the header for logging into unraid.

     

    Clearly I don't know how to use this app, since the only way I can get it to work, is a way it is not supposed to work.

  15. 5 minutes ago, jonathanm said:

    So you want him to rewrite the app just for you,  to work the way you want it to, when it works just fine using the recommended methods? It's honestly not as simple as you think it is, and you are the only person I've heard of to set up remote access this way. You are pretty much asking to commission a custom version of the app just for you.

    What way is it supposed to work?

     

    I have tried to put the ip and port in on unraid, and port 443 and it works fine. Except it will only use the root user, where I got nginx to handle it so I can use other users.

    I have tried to put the ip and port in the plugins says, and that does not work. So I assume this is wrong?

  16. 1 minute ago, jonathanm said:

    You are trying to bend the app to work the way you think it should, not the way it does. It's not simply a pass through mobile interface to the unraid GUI, it's a completely separate UI that works through the companion plugin.

     

    Normally you would set up a VPN from your mobile device to your home network, use ControlR or the normal webUI that way.

     

    Until limetech finishes securing the webUI, it's not recommended to expose it to the internet. They are working on it, but until they say it's ok, I wouldn't.

    It does actually work that way pretty well.

     

    Now I am trying to get the app to connect to the ip of my server on port 2379, but it silently fails and nothing gets added to the list.

     

    Logging into the gui in the plugin also show some problems.

    Unable to connect to serverx
    
    (1001) - Unable to get unRAID state (dockers): Get https://127.0.0.1/plugins/dynamix.docker.manager/include/DockerContainers.php: dial tcp 127.0.0.1:443: connect: connection refused

     

    Instead of the vpn, I am using nginx. With that I can easy login to the unraid gui, while also having pretty high security. Unraid isnt exposed directly to the internet, nginx is in between. With nginx I have set up multiple things that will block after a few failed attempts. Exposing directly isnt something I would recommend either.

  17. 2 minutes ago, jbrodriguez said:

    mikeydk,

     

    Try this ...

     

    In the Unraid Users page, set up a new user (mikey as in your example) and set a password for this user, a password that's different from root's password.

     

    Then, via any browser, access Unraid's GUI and try to login with this username/password (mikey/<password>).

     

    Does it work for you ?

    Are you trolling me?

  18. 15 minutes ago, jbrodriguez said:

    I understand what you're saying, but it's currently not possible.

     

    Authentication in Unraid currently only happens via 'root' user.

     

    That's out of my hands.

     

    It's unfortunate the app doesn't work for your use case.

    No you do NOT understand. Seriously, I dont know how to explain it more clear!

     

    I have tried multiple times to explain nginx is logging in as root to unraid, no matter what user I log into nginx with. Forget unraid, seriously forget it, dont think about it at all.

     

    The problem is the username field in the app, and the app not using what is in the field. This is where the problem is. Not unraid, not how unraid wants the username. The problem is the username the app is using to log in with, where it ignore the username field.

     

    1131635185_2019-06-0919_39_13.thumb.jpg.9ba471514d9043ed4a291d945feceb79.jpg

    No matter what I put into the username field, it is using "root".

  19. 12 minutes ago, jbrodriguez said:

    But the app needs to log into Unraid.

     

    That's why I mentioned that your scenario is not currently supported.

    Then why does it have a username field, when it isn't using it? All it need to support what I am doing, is to actually use what is put into the username field.

     

    Also PLEASE read it all. As I wrote "I don't need the app to log into unraid directly, nginx is taking care of that.". As I have tried to explain a few times now. nginx is logging into unraid with the root user, but I am not logging in with root to nginx. No matter what username I decide to create for nginx, unraid will still see root as the user logged in.

     

    I dont know how to explain this more clear.

     

    All I need, is the username field in the app to actually be used.

     

    I have tested it by creating a root user that could log into nginx, and the app worked perfectly. So what I am doing will work, if the app is using the username entered into the username field in the app.

     

    When I change the username in the username field, I can see in the log it is still using "root" as username, instead of what is in the field. I just need the field to actually be used as the username to log in with.