Jump to content


  • Content Count

  • Joined

Community Reputation

3 Neutral

About mikeydk

  • Rank
    Advanced Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. 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
  2. I just removed a disk1 from my array using the guide on the wiki. The guide included emptying the disk to remove, and setting all shares to only include other disks. I only got 2 disks in (+cache), and after my change I will have 1 disk+cache. After using the new config function I removed disk1 as I wanted, and then set disk2 as disk1. Setting disk2 to disk1 caused some problems. All shares were still set to use only disk2, but I didn't have the option to change that. The dropdown for include and exclude disks were both empty, while being marked as "All", but seemingly still only wanting to use disk2, which is no longer present.
  3. Seems to be something up with the plugin 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.
  4. 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 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.
  5. I dont think I ever said that. 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. 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.
  6. 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?
  7. 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 dial tcp 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.
  8. What does the username field in the app do?
  9. 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. No matter what I put into the username field, it is using "root".
  10. 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.
  11. I can edit the field, but no matter what I put into the username field, it will still continue to use root as username. Here I have put "mikey" in as username, which is then the username I expect it to try. But when I look in the log on the server, I see it trying to log in as "root", while the field is saying "mikey". I am not talking about unraid at all. The problem is the android app, where it does not use the username put into the username field. I don't need the app to log into unraid directly, nginx is taking care of that. I do not need the app to log in as root, nginx is taking care of that. I need the android app to use the username that is put into the username field. The problem is not connecting directly to unraid, the problem is the username field not having any effect on what username the app is trying to l og in with.
  12. The problem is in the app. No matter what username I put in, it will continue to use root as username.
  13. I did something like this years ago, back then I had an unstable fiber modem, which just stopped passing anything through. To restart that, I wrote some code in arduino, and flashed it to a Sonoff. It would then try to access google.com, and if it had failed connecting for a few minutes, it would kill power to the modem, wait 15 seconds, then turn it back on. After that it would give it 5 minutes to start up and get connection, if it didnt, it would be power cycled again.
  14. I can connect directly to it over my local network, and I can also connect to it over the internet through nginx, if I add a root user to the .passwd file. If I remove the root user from the file again, and put the username into the app which it should use, I can see in the logfile it still trying to use root as username.