July 8, 20223 yr Hi all, I have a problem with my unRAID machine. The docker NginxProxyManager stopped working since this afternoon, and the local webUI's all work, only the subdomains aint working. I've rebooted the server and now I got the following notification: Your server has detected hardware errors. You should install mcelog via the NerdPack plugin, post your diagnostics and ask for assistance on the Unraid forums. The output of mcelog (if installed) has been logged More Information Dunno what that means, other than something isn't working right because I can only access the webUI's of my dockers in my local network and not via the domains set via NginxProxyManager. I alredy re-installed NginxProxyManager a several times, but still only the local addresses work. I think that the server is okay, but that there is an error with above docker... My error I get from typing in my domains are ERR_CONNECTION_TIMED_OUT. But when I type in my public ip I get: Congratulations! You've successfully started the Nginx Proxy Manager. If you're seeing this site then you're trying to access a host that isn't set up yet. Log in to the Admin panel to get started. Powered by Nginx Proxy Manager So that seems to work. But typing the domains still errors out with the error mentioned above. Hereby attached the diagnostics from 8:42 PM local time, CET. diagnostics-20220708-2042.zip I've edit this post because I think nothing is wrong with the hardware of my server, but just with one docker image. Text edited is bold, as you can see above. Edited July 9, 20223 yr by rikdegraaff See bold text
July 9, 20223 yr Author Sorry for the doublepost, but I changed the topic big time. So not a kick up, but just other problems, I think. Hope someone can help me. Thanks.
July 9, 20223 yr Perhaps here? or here? You can find the correct support thread for your container by clicking on "Support" in the Unraid app icon drop down menu.
July 9, 20223 yr Author Solution Thanks @JonathanM for the information: It is about the docker image from Djoss, so that is my next stop. Greetings, Rik Edit: I've solved it, my router was reset a few days ago and missed one port setting for port 443, added that port to my router config again and ka-ching! Solved! Edited July 9, 20223 yr by rikdegraaff See edit
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.