-
Webui inaccessible. Able to SSH in. Perhaps an issue with EMHTTPD
I did this and had the same issue. I ran through a series of experiments to see if I could determine this issue. I removed and replaced drives, PCIe NVME cards, etc. It turns out that at least one of the issues I was facing is that my `cache_fast.cfg` file was causing issues. If I removed it, I could boot into a WebUI and do some further investigation. I went ahead and reinstalled all drives, swapping out the old, most likely dead drive, for a new one. I then booted up into a WebUI where those 4 drives do not form a cache. Hoping beyond hope to recover the data I found the following I was able to access the data on those 4 drives in this way. Please note that when it says: That the NVME drives work a little differently with respect to the adding of the '1'. Instead I ran an `lsblk` command and noticed a different value for my nvme drives of adding a 'p1'. That did the trick. I was able to access the contents and am in the process of RSYNC'ing them now so at least I can restore them. Thanks JorgeB PS I went to thank the creator of the other post and lo and behold it was JorgeB again. You are just like Roy Kent.
-
Webui inaccessible. Able to SSH in. Perhaps an issue with EMHTTPD
Yes, it is expected. My array is a Dell MD1200 JBOD. In my last attempt to troubleshoot I removed all excess peripherals including my JBOD
-
bambino53 started following Webui inaccessible. Able to SSH in. Perhaps an issue with EMHTTPD
-
Webui inaccessible. Able to SSH in. Perhaps an issue with EMHTTPD
Backstory. I had been having issues recently of the WebUI locking up and sometimes issues with VMs not booting. This week I ran into two issues that I finally shut down and did some physical reconfiguration. 1) One of my 4 NVME drives was showing as missing. 2) One of my windows VMs was no longer running properly. I popped the chassis out of the rack disconnecting all of the various peripherals, power and network cables. I removed all 4 NVME drives to determine the missing one and the Numbers displayed in UNRAID did not match any numbers shown on the sticks themselves. I guess at 1 and replaced it with a new NVME drive. I reconnected everything and rebooted. The WebUI never came up. I opened up my IPMI and validated that I was presented with a console logon screen. I also confirmed I was able to SSH into the system. I attempted to reboot with no change. I attempted a reboot in SAFE mode and no change. I attempted a GUI SAFE mode and was presented with a blank web page. Suspecting I screwed up something with the NVME drive replacement I reverted to the suspected bad drive. On reboot I had the same issues as before. I ran 3 passes of MEMTEST with no errors On digging a bit, I found that I could get something to happen by issuing the following commands `/etc/rc.d/rc.nginx` - would yield a NGINX 'no file found' type webpage (like when you misconfigure your proxy in SWAG) `/etc/rc.d/rc.php-frm` - would bring up the WebUI login at the normal address. Any attempt to login yielded a HTTP 502 error. With messages like "nginx: 2025/03/07 20:25:09 [error] 10520#10520: *1 auth request unexpected status: 502 while sending to client, client: 192.168.1.89, server: , request: "GET /Main HTTP/1.1", host: "192.168.1.100"" Based on some AI assisted research it seems the culprit may be a missing /etc/rc.d/rc.emhttpd I'm not sure however if that is the issue or if it is a symptom of something else. Attached are diagnostics from when this started and the last one from tonight. footeprint-diagnostics-20250304-0512.zip tower-diagnostics-20250304-1923.zip tower-diagnostics-20250307-2042.zip
-
[Support] binhex - PyCharm
I'll have to check out 'nginx proxy manager'. I started with the LetsEncrypt docker per SpaceInvader's videos. For anyone who finds my post I have an interim solution that I don't like but gives me necessary functionality. server { listen 80; server_name pycharm.mydomain.domain; return 301 https://$host$request_uri; } server { listen 443 ssl http2; server_name pycharm.mydomain.domain; proxy_redirect off; location / { proxy_set_header X-Forwarded-Proto https; proxy_pass http://*Docker IP:Port:*/; proxy_http_version 1.1; proxy_set_header Connection $http_connection; proxy_set_header Origin http://$host; proxy_set_header Upgrade $http_upgrade; } } I then access the NOVNC container @ https://pycharm.mydomain.domain/vnc_lite.html?resize=remote. The vnc.html page throws errors.
-
[Support] binhex - PyCharm
Does anyone have a valid pycharms.subdomain.conf file that successfully allows them to access NOVNC and subsequently PYCHARMS from outside their network? I've tried adapting several but nothing seems to work as they drop me to a page that says "noVNC encountered an error:" I'll edit this post later when I get home to add my current conf file. NOVNC does work when accessing from within my network.
-
[Support] jasonbean - Apache Guacamole
Thank you very much @Taddeusz. What you suggested worked wonders. I was hoping to use a subdomain rather than a folder to proxy ApacheGuacamole. As you said I scavenged bits and pieces from other examples and I came up with something that is working for me. I thought I should share it here in case anyone else is looking to do the same. "guacamole.subdomain.conf" server { listen 80; server_name guacamole.domain.org; return 301 https://$host$request_uri; } server { listen 443 ssl http2; server_name guacamole.domain.org; root html; index index.html index.htm; add_header Strict-Transport-Security "max-age=31536000; includeSubdomains;"; access_log /var/log/nginx/guacamole.access.log; location / { proxy_pass http://[IP Address]:[Port]/guacamole/; proxy_buffering off; proxy_http_version 1.1; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection $http_connection; proxy_cookie_path /guacamole/ /; } }
-
[Support] jasonbean - Apache Guacamole
I have been trying to get this up and running and I believe I have bypassed my initial concern. I loaded the docker and was unable to connect through to one of my virtual machines. The last time I had this working was before Unraid implemented docker by docker IP allocations. I tried to mimic this by setting the network type for this docker to Bridge; magically it all worked and I am able to connect to my virtual machines now. What I have to figure out now is how to make it work with Letsencrypt so I can reverse proxy it.
bambino53
Members
-
Joined
-
Last visited