wgstarks

Thanks. I was following @gridrunner's video guide. He didn't really go into detail about where the users were being created/modified. Makes a lot more sense now why it wasn't working. Thanks.

Still can't get this to work with "Local". Steps I took- 1) Completely deleted the docker, img and appdata folder. 2) Re-installed. 3) Logged into admin with default admin/password. 4) Set authentication to local. Saved and refreshed server. 5) Changed admin password via CLI. 6) Added new user via CLI. 7) Added same user via admin page with options "Allow Admin" "Allow Auto Login". Saved and refreshed server. 8 Attempted to login using newusername/password via https://<IP>:943. Login Failed. Logs show this- local auth failed: no stored password digest found in authcred attributes: auth/authlocal:35,web/http:1609,web/http:750,web/server:126,web/server:133,xml/authrpc:110,xml/authrpc:164,internet/defer:102,xml/authsess:50,sagent/saccess:86,xml/authrpc:244,xml/authsess:50,xml/authsess:103,auth/authdelegate:308,util/delegate:26,auth/authdelegate:237,util/defer:224,util/defer:246,internet/defer:190,internet/defer:181,internet/defer:323,util/defer:246,internet/defer:190,internet/defer:181,internet/defer:323,util/defer:245,internet/defer:102,auth/authdelegate:61,auth/authdelegate:240,util/delegate:26,auth/authlocal:35,util/error:61,util/error:44 Did I miss a step to setup local authentication? Looks like the docker isn't storing credentials locally but I have no idea why. Edit: Looks like I DID miss something. Just adding the password via SSH isn't enough. It has to be added in the admin page as well. Wonder what else I missed?

@ninthwalker Out of curiousity, I have a paid API for OMDB. Could I use this in conjunction with NowShowing to correct this?

Port forwarding probably, although I understand it can be run directly on some routers. @gridrunner has made a very good video. You can also checkout the OpenVPN-AS support thread.

OpenVPN-Access Server is a server so there is no need for paying for a commercial server. Once the docker is configured you would download authorization certificates to whatever client machines you want to use to connect back to your local network. I guess you could say you are the vendor.

Free license for 2 concurrent users so if access was very random you could probably have quite a few more.

I would suggest the openvpn-as docker to be able to use ControlR outside your local network.

Looks like best practice would be to disable auto updating and only update when you can also ssh and delete the default admin.

So, security wise there isn't really any difference between pam and local? Just a different location for storing the credentials?

How is this set in the server settings? Just asking so I can insure that I dont. Just to be sure I understand, you're saying the proper setup requires vpn connection to the local network and then login to the docker webgui? Or should it be impossible to connect to the webgui via vpn? I did some testing and I can connect to admin if I connect to lan via vpn first. Just want to be sure this is proper setup. I would prefer not to be able to access the gui at all under any circumstances from outside my LAN. Not sure if that's possible though? BTW- thanks for the help.

In that case wouldn't it just make sense to use "PAM" rather than "Local" authentication? My understanding is that the reason to use local was that users wouldn't have to be recreated/deleted after updating? This is quite a ways outside my knowledge level so I may be totally wrong. Maybe local is better anyway???

But won't the default admin user be recreated the next time the docker updates?

Watching this discussion I decided to test admin login via vpn connection. I vpn to my local network and can login to webgui docker admin using the admin/passwd I created when setting up the docker. How do I prevent access to this via vpn?

I'll give it another try. Do I need to do something more than delete the docker and image to remove users? Obviously did something wrong last time.

Yes. I actually deleted the docker and image (couldn't figure out how to just delete users). Re-installed the docker. Set verification to "local". And then added users and downloaded and installed new ovpn files on the clients. If auto-login is disabled authentication fails with the error posted above. The only way I could connect is enabling auto-login and PAM.

Ran into an issue with user credentials being lost. Did some searching and found this in the readme (missed it at first)- It looks like that will fix my problem with user accounts surviving docker updates but what about the admin account? Will this also preserve admin password or is there a better way? Edit: Switching authentication to local doesn't seem to work. Every time I tried to login it would get denied. local auth failed: no stored password digest found in authcred attributes: auth/authlocal:35,web/http:1609,web/http:750,web/server:126,web/server:133,xml/authrpc:110,xml/authrpc:164,internet/defer:102,xml/authsess:50,sagent/saccess:86,xml/authrpc:244,xml/authsess:50,xml/authsess:103,auth/authdelegate:308,util/delegate:26,auth/authdelegate:237,util/defer:224,util/defer:246,internet/defer:190,internet/defer:181,internet/defer:323,util/defer:246,internet/defer:190,internet/defer:181,internet/defer:323,util/defer:245,internet/defer:102,auth/authdelegate:61,auth/authdelegate:240,util/delegate:26,auth/authlocal:35,util/error:61,util/error:44

Which fan is revving? Looks like the ipmi status is showing that fan3 has failed.

I believe just the "Lower Non-Critical". See if that helps after you save the settings.

Hope that helps. You will see a section for each fan in the config file. I would recommend noting the original settings just in case you need to change them back.

When you go to settings click the "Readings" tab- Then select "Sensors Config"- This will open a configuration text file that you can edit- Just scroll down to the appropriate fan section, edit the threshold settings and save.

Perhaps their tech support people are wrong? I contacted them initially and was informed that SuperMicro doesnt provide a mac version of IPMIview. The only version I could find on their website that I could use was for iPhone. Moot now since SM hasn't updated IPMIview to be compatible with the html5 browser. Just for reference though, maybe you could provide a download link for the Mac version. I'm sure that SM will update it when the current firmware comes out of beta.

Must have got it right just by dumb luck then.

Trying to install the DuckDNS docker. Must be doing something wrong. Entered the subdomain (only one) and token and select "apply" but nothing happens, just get an xml and command. Edit: I guess third times the charm? Maybe it was being updated or offline for some reason? It finally downloaded and installed.

ControlR=2.7.0 iPhone iOS=10.3.2