ljm42

Hi, this will be fixed in the next My Servers plugin release. Thanks!

Yes. The LE certificate is only valid for myunraid.net urls, if using a different url then it uses a self-signed cert.

Certificate provisioning and renewals have been stable for the last eight hours, woot! https://status.unraid.net/ We made some changes that should result in increased stability going forward. But I'll go ahead and mention... if at any time you lose access to your server's webgui via your personal myunraid.net url, see this page: https://wiki.unraid.net/My_Servers#How_to_access_your_server_when_DNS_is_down

The "unexpected token" message means you are accessing the server via a URL that it is not configured to use. I'm excited to say that this error message will be much improved in the next My Servers plugin release. Open a web terminal and run: unraid-api report -vv In the ALLOWED ORIGINS area of the report it will list out the configured urls. I'm guessing you are using a url that is not in that list?

Unraid's WireGuard solution is not Docker based, although some community members have created Unraid containers as an alternative to the built-in solution. If you would like to use Unraid's built-in WireGuard solution, start here: https://forums.unraid.net/topic/84226-wireguard-quickstart/

Your system is in Strict mode, so https://ipaddress is not defined as that url is not valid for the myunraid.net certificate. You can use http://ipaddress (note http not https) to be redirected to the myunraid.net url. If there are DNS issues and the myunraid.net url is not available, see https://wiki.unraid.net/My_Servers#How_to_access_your_server_when_DNS_is_down

Sorry for the trouble. We are aware that some people are having issues with disconnects. We are working on a new release that should resolve this.

Thanks, we'll keep an eye out for that. BTW the easiest way to restart the api is `unraid-api restart`

Sorry folks, the service is bouncing. You can track the status here https://status.unraid.net/ I believe that everything is working fine for most people, unless you got unlucky and happen to be provisioning/renewing right now. Then there are intermittent issues. We are actively working on this. If you lose access to the webgui during this time please see https://wiki.unraid.net/My_Servers#How_to_access_your_server_when_DNS_is_down

To clarify, that is the contents of /var/log/wg-quick.log ? I do not recognize that at all

Are you using VMs? Any with GPU passthru? Would you know you were having errors if you weren't looking at that log file?

OK that part solved Are VMs enabled on this system? Actually, please upload your diagnostics (from Tools -> Diagnostics) Would you know you were having errors if you weren't looking at that log file? It may be that other systems are getting this and not realizing it. Please show a screenshot of your server tile on https://forums.unraid.net/my-servers/

If you want to use http://tower.home instead of http://tower.local, go to Settings -> Management Access and change the "Local TLD" from "local" to "home" (this assumes you have DNS that can resolve tower.home to the correct IP address.) All of the tower.local entries in ALLOWED_ORIGINS will change to tower.home and My Servers will work with that url. Once you make this change and are always accessing the system via a URL in the ALLOWED_ORIGINS, does that solve the problems you are seeing?

Were you connected via a web terminal when you did this? If so you want to do `/etc/rc.d/rc.nginx reload` rather than `restart`. If you were using a full ssh client then a restart should have been fine. I think you are probably having RAM issues, but perhaps someone else can chime in.

There are many ways to do reverse proxies, and many ways to mess them up This is the reason we created the My Servers Remote Access feature, so we could offer a simple solution that would work for most people. You are welcome to use an alternate solution, but I can't really comment on it / support it. One thing I will mention is that the My Servers client does not currently support reverse proxies, so you will get an error message when clicking on your username in the upper right corner of the page. We'll add support for that later, but at this point you'll probably want to uninstall the My Servers plugin if using your own reverse proxy.

Open a web terminal and run: unraid-api report -vv (don't post the output of that command with -vv). Look in the ALLOWED_ORIGINS area of the report, it will show the exact urls that are allowed to be used. Are you using one of those urls or something else? If you are using one of the listed urls to access the server, post the output of: unraid-api report -v note there is a single -v there. Where did you get this output?

Sorry for the trouble folks. This is the exact issue, trying to track down why new users are getting this.

The ip.hash.myunraid.net naming scheme was designed with privacy in mind, so our DDNS server cannot be used to locate a given user's server. i.e. you have to know the IP in order to find the server. We expect the My Servers Dashboard will make this a non-issue for most people. I'm sorry if it isn't ideal for your use case, but we are putting privacy first on this one.

This link is from the Custom Networks portion of the OP: https://forums.unraid.net/topic/84229-dynamix-wireguard-vpn/page/8/?tab=comments#comment-808801

I don't understand the question? Once you have migrated from the old unraid.net certificate to the new myunraid.net certificate you are fine.

I need to see your your wg-quick.log, see my previous posts in this thread thread on how to get it

There is an "import tunnel" button right next to "add tunnel"

Please read the first two posts in this thread very carefully, particularly the part titled "Complex networks"

Sorry for the trouble. Are you sure the new certificate is working properly? Try restarting your browser or using a different browser and see if there are warnings you have to accept. If the certificate is working properly I wouldn't expect the URL change to cause issues with the Unraid API, particularly after you've restarted it. That implies the issue is not related to the certificate change. We are working on some pretty big internal changes for the API that will hopefully resolve this for folks.

I'd recommend using the My Servers Dashboard: https://forums.unraid.net/my-servers/ as your starting point, it will have the correct URL within about 10 minutes of it changing.