MsDarkDiva
-
Posts
24 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by MsDarkDiva
-
-
1 minute ago, trurl said:
Your router, if it is directly connected to the internet, should have a public IP (WAN), and that public IP is given to it by your internet service, so you don't reassign your router IP. (A router will typically have an internal private IP as well so you can manage it inside your LAN.)
The devices connected to your router should have private IP addresses assigned to them. Simplest is just to use DHCP and let the router choose a private IPs for your devices.
Since you seem to be using a public IP not owned by you, quite likely the reason you can't connect to your server is because when anything tries to access something with that IP, it is trying to access the owner of that IP in Norway.
My network has had no issues connecting to my router/internet for a few years now with similar IPs. Everything else after the outage connected again just fine and most of my devices are assigned static IPs. I'm new to Unraid and after doing a little research, I read that it was best to leave the server unassigned on the router, so I did that, however I left the address on the server.
I do have the ability to reassign my router's IP for my LAN network (which yes, usually have an internal private IP). -
1 minute ago, trurl said:
How did you get that IP? You can't just randomly choose public IPs for yourself. Assigning IPs to yourself should be restricted to private ranges.
Looks like it belongs to a company in Norway.
I will reassign another IP to my router, hopefully, after this is all over and I reconnect to my server. -
Just now, trurl said:
But your server IP is not a private IP.
No. My server IP is not a private IP, I understand this now. However, it is the IP of my network.
-
1 minute ago, John_M said:
Not really. It's the crux of your problem.
OK. So you have a single public IP address allocated to your router. But you say you also have it allocated to your server. That can't possibly work.
The IP address allocated to my router from my internet service provider, is not the same as the addresses on my private network. My apologies if I didn't make myself clear.
-
3 hours ago, John_M said:
What IP address does you Windows PC use, then? Do you have multiple public IP addresses allocated by your Internet service provider? Since IPv4 addresses are now quite a scarce commodity, a typical user would have a single public IP address allocated to their router. The local network would then use one of the reserved private address ranges. I'm just trying to work out how you're connecting to your server.
No I do not have multiple public IP addresses allocated by my internet service provider. Yes, I have a single public IP address allocated to my router. My Windows PC uses a similar address to the server on my local network. This address issue has thrown everything well off topic! LOL! -
2 hours ago, trurl said:
I don't doubt that is your IP address. I was just wondering if by having your server on a public IP address you have allowed yourself to be hacked.
This all came about because of a power failure. I lost power in my apartment for a few minutes. When my server came back online I could no longer access it through the WebUI. So I'm hoping I can get help reconnecting with it. I'll definitely have to invest in a UPS, lesson learned!
-
3 hours ago, trurl said:
Could you explain further why your server has a public IP?
Are you sure you haven't been hacked?
No. Not hacked at all. That is my IP address.
-
Okay. So I'm still fighting with this. I did everything as mentioned in this post: Power outage Unraid won't connect to internet
On 3/5/2021 at 8:30 AM, Frank1940 said:Make sure that the cat5 cable is securely plugged in on both ends.
Try a new cable between the server and the switch.
Swap cable to a new port on the switch.
Reboot the switch (Cut power and wait thirty seconds is usually required to do this.)
Double check the lights (and their pattern) on both ports at the ends of the cable. You may have to check the user manuals to determine what is normal. (May require download from Manufacturer!)
Power EVERYTHING down on the network. (DON'T pull plugs on any computer/server. You should be able safely power them down if required by pushing the power switch on the case for about one second.) Wait one minute. Power back up starting with the router. Wait two minutes. Now power up the switch. Wait one minute. Power up the server. Wait five minutes. Now power on the PC's. You can do the PC's at intervals as you need them. (I would start with the one you need to test with first...) IF you don't have a connection to the server. Double checked its IP address. You can do this from the console (keyboard and monitor) by typing the following command (after logging in):
ifconfigLook at the IP addresses. You are looking for one that begins with either 192.xxx.xxx.xxx or 10.xxx.xxx.xxx If you only find ones that begin with 172.xxx.xxx.xxx or 127.xxx.xxx.xxx, that is a problem with the physical network.
There was no change after powering everything off/on. When I put in the ifconfig command in the console my IP address wasn't there. The address listed were br0 inet 169.xxx.xxx.xxx, br-13* inet 172.xxx.xxx.xxx, docker0 inet 172.xxx.xxx.xxx, lo inet 127.xxx.xxx.xxx, shim br0 inet 169.xxx.xxx.xxx and virbr0 inet 192.xxx.xxx.xxx (which is not my IP). -
Yes, I do. Although I didn't reserve the address on my router, just on the server.
Update: I deleted the network.cfg file, but there has been no change. I also assigned the IP my DHCP server and rebooted my router to see if that would help, but I'm still getting a timeout message when I try to ping it. -
35 minutes ago, John_M said:
Your diagnostics show that your server has a static IP address. Curiously, the address is a public one, (212.xxx.xxx.44). That's unusual. Is it intentional? Can you ping it using that address? Your disks and boot flash appear to be good and as far as I can tell the start-up is normal. If you need to reset networking you can delete the network.cfg file in the config directory on the flash and it will be recreated with DHCP enabled when you reboot.
Yes, the IP is intentional. When I try to ping it I get "request timed out". Should I still delete the network.cfg file? -
Hi! I'm on Unraid 6.8.3 and my system (QNAP TS-453D) rebooted after a short power failure, but since then, I've been unable to access the server through the webui or through file explorer (Win10). I tried rebooting my router and it can see the server. After a search I tried the /etc/rc.d/rc.nginx restart solution mentioned here: Lost Unraid GUI after power outage [Solved] but it didn't work. My parity disk was removed at the time of the outage, as I'm in the process of transferring a large amount of media files. However, it wasn't transferring files at that time. I connected to the console and ran a diagnostic.
diagnostics.zip -
18 hours ago, MsDarkDiva said:
Hi!
I have Emby running, use swag (nginx) as reverse proxy and Authelia as 2FA. I can access it via my localip:8096, but when I sign in by my subdomain, although Authelia doesn't give me a problem, when it redirects I get a 502 bad gateway error. In the nginx log I see this:2021/03/08 15:36:07 [error] 510#510: *209 emby could not be resolved (3: Host not found) while sending to client, client: 94.247.177.39, server: emby.*, request: "GET / HTTP/1.1", host: "emby.myusername.com", referrer: "https://emby.myusername.com/authelia/2fa/push-notification?rd=https%3A%2F%2Femby.myusername.com%2F"
2021/03/08 15:36:07 [error] 510#510: *209 emby could not be resolved (3: Host not found) while sending to client, client: 94.247.177.39, server: emby.*, request: "GET /favicon.ico HTTP/1.1", host: "emby.myusername.com", referrer: "https://emby.myusername.com/"I'm sure I broke something after adding Authelia, but I don't know what to fix or what's missing.
Nevermind! I tinkered for a while and finally got it working. Thanks anyway.
-
On 3/4/2021 at 6:48 PM, zerosk said:
EDIT: I let the container sit there for 15 minutes and it seemed to start working, albeit quite slowly. Only a couple of my torrents have downloaded the metadata and even then they are running quite slowly. But when I turn on my PIA VPN from another computer on the same network and connect to the same node, I can run a speedtest and get 700 down/350 up. I don't know why it's behaving so strange.
EDIT 2: Things appear back to normal after about 30 minutes. Potentially just VPN problems or issues with the specific torrents in question maybe
Thanks for the updates. Unfortunately, no matter what I did or how long I let it sit, it never got working. After doing more research, I found the problem is not uncommon, but the suggested fixes didn't work for me... So, I switched to Deluge, which worked right off the bat. I may try it again at some point, however I'm just beginning to set everything up, which is enough of a challenge!
-
Hi!
I have Emby running, use swag (nginx) as reverse proxy and Authelia as 2FA. I can access it via my localip:8096, but when I sign in by my subdomain, although Authelia doesn't give me a problem, when it redirects I get a 502 bad gateway error. In the nginx log I see this:2021/03/08 15:36:07 [error] 510#510: *209 emby could not be resolved (3: Host not found) while sending to client, client: 94.247.177.39, server: emby.*, request: "GET / HTTP/1.1", host: "emby.myusername.com", referrer: "https://emby.myusername.com/authelia/2fa/push-notification?rd=https%3A%2F%2Femby.myusername.com%2F"
2021/03/08 15:36:07 [error] 510#510: *209 emby could not be resolved (3: Host not found) while sending to client, client: 94.247.177.39, server: emby.*, request: "GET /favicon.ico HTTP/1.1", host: "emby.myusername.com", referrer: "https://emby.myusername.com/"I'm sure I broke something after adding Authelia, but I don't know what to fix or what's missing.
-
I'm having issues getting qBit to download from Sonarr/Radarr etc. The containers are running through PrivoxyVPN. Sonarr grabs the files and qBit receives the requests, but the files keeps getting stuck on "Downloading Metadata" and nothing happens. I've checked to see if Privoxy is running and it's enabled via the webui. When I test a torrent link through Ipleak, I can see that qBit is using the proxy/VPN.
I have qBit's incoming connection port set at 9585, but I've noticed that Ipleak always lists the port as 1 (even if I set the container to use random ports on start up). I've included the logs after a fresh start up. -
...Aaand the fix has stopped working! qBit and the indexers are no longer connecting for me again. I changed qBit back to my original host ip address and it connected right away. I don't know what's going on.
-
17 minutes ago, Ao27893 said:
I guess it finally caught up to all of us.
9 minutes ago, bmoney003 said:im having the same issues with radarr and nzbget and deluge. will not connect. this is as of friday as well.
Here are the answers from the faq:
QuoteQ25. I have recently updated my Docker image for DelugeVPN/PrivoxyVPN/SABnzbdVPN/qBittorrentVPN and can no view the Web UI for the application i am routing through the VPN container, why is this and how can i fix it?.
A25. Due to iptables tightening it is now a requirement that you add the Web UI/API ports for the application you want to route through the VPN to the 'ADDITIONAL_PORTS' env var value for the VPN container, if you have multiple ports then please separate the values with a comma, e.g. 'ADDITIONAL_PORTS' = 1234,5678
The other change you will need to do is when defining connections from an application to another application in the same container network (as is the case in this scenario) then you will need to set the host to 'localhost' and NOT the LAN IP address, this is because the applications are now bound to the same network and thus should communicate over 'localhost'.
Please also review A24. above, and ensure you have completed ALL steps to route a container through another one.
Q26. I have recently updated my Docker image for DelugeVPN/PrivoxyVPN/SABnzbdVPN/qBittorrentVPN and have setup Sonarr/Radarr/Lidarr...etc to use Privoxy (proxy server), but this is now no longer able to connect to the 'Download Client' (e.g. Deluge, rTorrent, qBittorrent, SABnzbd), why is this and how can i fix it?.
A26. Due to iptables tightening you need to now bypass local addresses for proxy connection in index applications, for Sonarr/Radarr/Lidarr this can be achieved by editing the value for 'Ignored Addresses' under the Settings/General/Proxy and entering in the IP address of the unRAID server running the VPN container. This will then bypass using Privoxy (proxy server) for connections to the local server, and thus allow a direct connection to the download client.
An alternative method to this is to setup Jackett, then configure Jackett to use Privoxy. You then simply point Sonarr/Radarr/Lidarr...etc at Jackett as an 'Indexer' and you are done, there is NO need to configure a proxy for Sonarr/Radarr/Lidarr...etc in this configuration, as Jackett is already doing the proxying for you.
-
2
-
-
On 2/26/2021 at 11:33 AM, brawny said:
To resolve, I noticed that when I looked at "Status and Interface Options" in the SABnzbd UI, the local IPV4 address was a 10.8.x.x address. I had this set as the 192.168.1.x address of my server in Radarr and Sonarr (and I'm sure this is how it has always been!). I copied/pasted the 10.x.x.x address into the SAB config in Sonarr and Radarr, and lo and behold, they were able to connect and started to work...
Not sure how this happened, but glad it is...
I'm not sure why this has happened as well. Everything was working and suddenly something changed and I started getting 503 errors. All of my *arr containers could no longer connect with qBittorrent, plus, all of the indexers that I set up failed. By using the 172.*.*.* ip of the container in qBit, I am now able to connect, but how do you change the address in Jackett? Do I have to manually change the url of each indexer to update it to the 172.*.*.* address?
-
9 hours ago, sansoo22 said:
@MsDarkDiva - If you're on Win10 you might give Visual Studio Code a try for editing config files. Especially anything yaml. VS Code is free, easy to setup, and for yaml it does cool things like auto-indent 2 spaces whenever you hit the tab key. It would have even highlighted the word "password" in your example above as an error.
THIS! I definitely need something to tell me when I'm making a mistake! Downloading it now. Thanks!
-
22 hours ago, Sycotix said:
Your backend file config is not correct. It needs to look like this:
file: path: /config/users_database.yml password: algorithm: argon2id iterations: 1 key_length: 32 salt_length: 16 memory: 1024 parallelism: 8You have entered a password after the 'password:' line. The passwords are saved in the actual backend file only.
I appreciate your assistance and patience Sycotix. I fixed the line as you instructed, which worked. Then I spent then I spent the rest of the day chasing errors (special characters in my passwords, my Gmail needed it's own app password to work and then my user credentials were bad...). All this to say, I finally got Authelia to start! The struggle isn't over, but thank you!
-
On 2/3/2021 at 4:39 PM, Sycotix said:
Glad to hear it! You just taught me something too!
Enjoy
Well, I got a little farther. I followed your video which made editing everything much easier! However, when I try to start Authelia I get: "Error malformed yaml: line 200: did not find expected key". The only thing at line 200 for me is a comment hashtag. Is it referring to something else?
-
14 hours ago, Sycotix said:
Hi there and welcome to unRAID!
This can often happen because of permissions applied by unRAID/Docker.
One the ways I combat this is using the Krusader container from the App Store. It allows you to view/edit your files and have full permissions.
So I would install Krusader then when you open it, navigate to your appdata folder (mnt/user/appdata/authelia) and simply delete the config file. On your Windows 10 machine, once you've finished creating your config file just copy it into the appdata folder for Authelia. It should keep the right permissions so you can continue editing and saving as you go.
Just be really careful in Krusader that you DO NOT delete or move anything accidentally. Always make sure you are accessing the user share folder like above and not any of the disk folders.
There might be a more elegant solution but it works.
Thanks for this Sycotix!
I had Krusader installed, so I navigated to the configuration file and under properties, I found that it actually allows you to change file permissions for the Owner, Group and Others. Once I changed that, the file opened up no fuss. Now, comes the task of editing the file properly, so your video has come out just in time! -
Hi,
I am very new to Unraid and I have just begun following the instructions to install Authelia. For some reason, I am getting a "You do not have permission to open this file..." error, when trying to edit the configuration.yml, using Notepad++ on Windows 10. How do I fix this? I know I am probably missing something basic.
Unable to access Unraid WebUI after power failure [Solved]
in General Support
Posted
Thank John_M. Your post gave me an idea to see if the NIC was truly damaged. I powered down the server and removed the Unraid OS usb. Since it's a Qnap it reverted to it's original OS and I was able to find the server on my network via the Qfinder Pro tool. When I rebooted once again with the Unraid OS installed, it immediately appeared again on my network and I am able to access it again via the WebUI, so thank you!