Everything posted by powderwt
-
Unable to access GUI - Recently updated after long hiatus to 6.12.13 ?
Any suggestions for where to look as far as what could be causing the problem? It was all fine until i updated, really prefer to not have to go through all the trial and error that involves as it will mean alot of up and down of the things im hosting.
-
Unable to access GUI - Recently updated after long hiatus to 6.12.13 ?
@DivideBy0 netstat -anp | grep LISTEN | grep 80 tcp 0 0 0.0.0.0:9897 0.0.0.0:* LISTEN 16880/docker-proxy tcp 0 0 0.0.0.0:8070 0.0.0.0:* LISTEN 15821/docker-proxy tcp 0 0 0.0.0.0:8060 0.0.0.0:* LISTEN 15854/docker-proxy tcp 0 0 0.0.0.0:1880 0.0.0.0:* LISTEN 13238/docker-proxy tcp6 0 0 :::43803 :::* LISTEN 6396/rpc.statd tcp6 0 0 :::8070 :::* LISTEN 15830/docker-proxy tcp6 0 0 :::8060 :::* LISTEN 15861/docker-proxy tcp6 0 0 :::1880 :::* LISTEN 13246/docker-proxy unix 2 [ ACC ] STREAM LISTENING 40671 16493/containerd-sh /run/containerd/s/f0d79bea468cd1831218588ccab627d193c780425a6e2bc9e8462896e72c2b98 unix 2 [ ACC ] STREAM LISTENING 45434 17451/containerd-sh /run/containerd/s/3398050e0b58bfe0434e7d4262fb539d3fa9b4fb8f274c4fcc34fc6202792a15 **Nothing Returned here** netstat -anp | grep LISTEN | grep 443 tcp 0 0 0.0.0.0:18443 0.0.0.0:* LISTEN 13194/docker-proxy tcp6 0 0 :::18443 :::* LISTEN 13201/docker-proxy # /etc/rc.d/rc.nginx restart Nginx is not running emhttp stop Nginx is not running Gracefully shutting down php-fpm done Stopping emhttpd rmmod: ERROR: Module md_mod is in use **Brief pause, but did not output anything** wget 127.0.0.1:8008 --2024-11-25 15:05:58-- http://127.0.0.1:8008/ Connecting to 127.0.0.1:8008... failed: Connection refused. wget 127.0.0.1 --2024-11-25 15:06:19-- http://127.0.0.1/ Connecting to 127.0.0.1:80... failed: Connection refused.
-
Unable to access GUI - Recently updated after long hiatus to 6.12.13 ?
Just tried as you directed utilizing a fresh imaged usb with the new unraid usb creator tool. Able to access the web UI no problem both via tower.local and my set IP of 192.168.1.64
-
Unable to access GUI - Recently updated after long hiatus to 6.12.13 ?
Please hold, will be shutting down and putting my original flash drive in to try this.
-
Unable to access GUI - Recently updated after long hiatus to 6.12.13 ?
That is correct sir. I have tried utilizing my local ip: http://192.168.1.64:8008 to no success but also tower.local
-
Unable to access GUI - Recently updated after long hiatus to 6.12.13 ?
I had not done anything with my unraid server for several years- everything was running just fine no need for any changes to unraid anything. However, i recently decided to get on and decided to upgrade as i had put it off for so long, IIRC It was previously running on v5 something or maybe even 4? Anyways, the server i running just fine under the hood. I can SSH into it normally, login via direct access as well. Something seems to be broken however as I can not access my Web GUI. All my dockers and everything are running just fine however. I saw some release notes mentioning turning ssl off > (If memory serves me here: use_ssl off but i am still unable to access the web ui. performing netstate -grep returns: ~# netstat -grep Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface default OPNsense.kronoc 0.0.0.0 UG 0 0 0 shim-br0 default OPNsense.kronoc 0.0.0.0 UG 1008 0 0 br0 REDACTED 0.0.0.0 255.255.255.255 UH 0 0 0 wg0 REDACTED 0.0.0.0 255.255.0.0 U 0 0 0 docker0 REDACTED 0.0.0.0 255.255.0.0 U 0 0 0 br-e2d3fd4035e1 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 shim-br0 192.168.1.0 0.0.0.0 255.255.255.0 U 1008 0 0 br0 192.168.122.0 0.0.0.0 255.255.255.0 U 0 0 0 virbr0 I feel as though the br0 interfaces dont quite seem right? I am attaching the diagnostics zip to my post as customary. Anything else i can provide please let me know. tower-diagnostics-20241125-1308.zip
-
[Support] binhex - DelugeVPN
Correct, I tried downloading packages for: netherlands, CA_montreal, CA_toronto, and a couple others to no avail. The client.ovpn file is an ovpn file I managed to find in my backups that I had saved and decided to give it a go since it was known working with that prior.
-
[Support] binhex - DelugeVPN
seems to still be happening, even though ive updated both endpoints to several new ones, and a new .ovpn file supervisord_01_17_2021_Censored.log
-
[Support] binhex - DelugeVPN
My apologies, here is the full supervisord: supervisord_01_16_2021.log
-
[Support] binhex - DelugeVPN
Been having some issues the past 5 days or so not being able to connect to deluge webui. Verified i was on the ``latest`` branch also tried reinstalling deluge to no avail. Believe it has something to do with this bit of the supervisord log, with openvpn updating to 2.5.0? Im using mullvad vpn fwiw... deluge_supervisord_censored_snippet
-
**VIDEO GUIDE How to route any container through the network of another (VPN)
Did you try adding " ... .1:8080/web/ " To the end? Or whatever your ip:port may be? @Simon Forest
-
**VIDEO GUIDE How to route any container through the network of another (VPN)
When you do this in my experience, being able to click on the program in your docker tab and go to webui, will no longer work. Instead, you will have to verify that is is indeed running, and then open a new browser tab and navigate to your server ip, and then the port of the program in question(VNC) EX: 192.168.1.1:34400/web/ The example I just made, is how I access one of the dockers I have setup this way, but I believe that should get you close enough to be able to figure out what you're trying to do.
-
**VIDEO GUIDE How to route any container through the network of another (VPN)
Curious, do you have binhex-privoxyvpn AND delugevpn? I already had deluge setup and have been trying to setup privoxy to start pointing containers to it instead, but was reading a comment from binhex himself saying not to change the container ports cause it wont work, but deluge uses the same 8118... But trying to utilize Spaceinvader's method with deluge, i cant access the webui as he specified at all on anything i have tried so far... Most particularly, im trying to get xteve docker setup using this.
-
DiskSpeed, hdd/ssd benchmarking (unRAID 6+), version 2.10.10
So im having a weird issue where the drive img's load for a split second and then disappear. This happeneds everytime i open the docker, or refresh the page?