July 25, 2025Jul 25 Setup and information:1. Using a raspberry pie locally. I have my router pointing to it to resolve dns and local dns records2. Recently switched from ISP router hardware to TP-LINK.a. Setup VPN on TP-Link using wireguard configurations. In turn, i turned them off on the server.b. I have reason to believe that TP-LINK might be stopping rebinding. I do not see an option to turn it off eitherc. I went ahead and port forward connections that i needed to my server IP. IE: 81 and 444 are forwarded and handled by Nginx Reverse Proxyd. Ports for unraid connection for FQDN have been forwarded as well.e. Ports for standard, non-FQDN have been forwarded as well.i. Note that i do not use standard ports.3. I have to turn of strict on management access. Setting it to yes at least allows me to VPN into the router and access the server from there.4. I just noticed that when turning on Dynamic Remote Access I can no longer turn it off... weird.5. Lastly, on Unraid Connect, it does seem like I am getting info from my router.I do hope i did this diagnostic stuff right. I pray im not releasing a bunch of info...The guide I followed:https://docs.unraid.net/connect/remote-access/tower-diagnostics-20250724-2005.zipUpdate: a partial resolution for fully qualified domain name on land was resembled by reinstalling unraid connect. I found this out by tracking the system logs and seeing that there is an issue with nginx communication. When verifying the validity of nginx, I found that there is a malformation in the config file. Since then I have went ahead and forced nginx to do a update via terminal commands. I have forgotten what terminal commands those are but it has put itself in a state in which it is wrong again and well formed. But at least I have lan fully qualified domain happening so that my certs are good and I don't have navigate to a "unsaved site".Update 2: I learned that unraid connect is adding duplicate records to my nginx. /etc/nginx/conf.d. It is only by deleting those files and reinstalling it does it seem to half fix itself. Once i try connecting from outside WAN. those files are duplicated causing nginx to start throwing errors for duplicate records in the sys log. This seems to potentially be a bug with the app itself. im wondering if reverting a version will resolve this Edited July 25, 2025Jul 25 by Thomas T Update 2
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.