ljm42

We are working on a fix for nginx with IPv6 but for now you should go to Settings -> Network Settings and change eth0 to "IPv4 only" if that works in your environment.
 
Also, please see my comment here about browsers potentially causing issues with backgrounded tabs:
https://forums.unraid.net/bug-reports/stable-releases/612-unraid-webui-stop-responding-then-nginx-crash-r2451/page/3/?tab=comments#comment-25245
 

Unrelated to the release, you can turn help on/off by clicking the question mark icon in the upper right corner of the page.

Fix Common Problems has the answer:
Fix Common Problems: Error: macvlan call traces found  
See this from the 6.12.0 release notes:
https://docs.unraid.net/unraid-os/release-notes/6.12.0#call-traces-related-to-macvlan

The webgui has blocked iframes for some time now.
 
In 6.12 or with the Connect plugin installed, there is an exception to allow connect.myunraid.net to iframe it. There isn't a config option to allow other websites to iframe it.

This is part of a call trace related to macvlan. See this part of the 6.12.0 release notes:
https://docs.unraid.net/unraid-os/release-notes/6.12.0#call-traces-related-to-macvlan 

Hey everyone, Unraid 6.12.1 should resolve the issues in this thread:
https://forums.unraid.net/topic/140824-unraid-os-version-6121-available/
 
Well, unless you are running SSL on port 445, you'll still need to tweak that setting to prevent a conflict:
https://forums.unraid.net/topic/140510-complete-webui-breakage-after-6120-update/#comment-1271735
 
If you can't currently access the webgui in 6.12.0, see the manual upgrade process here:
https://docs.unraid.net/unraid-os/manual/upgrade-instructions/#manual-upgrade-or-downgrade
 
If you continue to have issues, please start a new thread and be sure to include your diagnostics.zip from 6.12.1

Let's see if this helps...
 
This is the url to your Unraid webgui:
  https://ip-dashed.hash.myunraid.net:port
 
This is the url to your docker container's webgui:
  https://myip:port/somepassboltgeneratedhash
 
They are not related in any way. The certificate used for the Unraid webgui has no bearing on the certificate used for the docker container.

Since you are having issues with the Passbolt container, I'll recommend that you ask your questions in the support thread for that container:
  https://forums.unraid.net/topic/119569-support-smartphonelover-passbolt/
The folks there will be the most knowledgeable about how to configure SSL for that container.
 

This can definitely work. So eth0 on each server should be connected to your normal switch. If eth0 on both is 10g and you have a 10g switch then I wouldn't bother with the steps below. But if one or both servers can't connect to the main network at 10g then the steps below will let the two servers talk to each other at 10g while still using eth0 to talk to everything else.
 
Direct connect the 10g nics on each server and statically assign them to a new subnet with unique IP addresses and no gateway.
 
In my case, my eth0 IPs were:
server1: 192.168.10.50 server2: 192.168.10.160  
So I made my direct-connected 10g eth1 IPs:
server1: 192.168.11.50 server2: 192.168.11.160 so it would be easy to keep them straight.
 
I generally say to avoid jumbo frames, but since this subnet will *only* have these two computers on it, as long as you change the MTU of both to 9000 then jumbo frames should give a small speed boost. It is critical that every computer on this network have the same MTU.
 
When connecting between the systems it is *important* to use the IP addresses on this subnet and not a name like "tower". You want to be sure the servers actually talk over this network.
 

 

nginx: 2023/06/15 10:08:43 [emerg] 3876#3876: bind() to 127.0.0.1:445 failed (98: Address already in use)  
nginx is unable to start SSL on port 445. When picking custom ports for things, it is best to use high numbers (over 1000, less than 64,000) that will never conflict with built-in ports.
 
I'd recommend carefully editing config/ident.cfg on your flash drive and changing:
PORTSSL="445" to something higher, like:
PORTSSL="3443" (assuming that isn't in use by a Docker container)
 
Once that is done you may be able to get the webgui by typing:
/etc/rc.d/rc.nginx reload Or it may take a reboot.

You can't use WireGuard to join two networks that have overlapping subnets.  So if one is 192.168.1.x and the other is 192.168.2.x then you are fine (assuming the subnet mask on both is 255.255.255.0). 
 
But if both networks use 192.168.1.x then you can't join those networks.  In that case you can use the "Remote Access to Server" option and connect to the server via the server's tunnel ip. You will have access to the server only, nothing on the remote network.

You can probably disable the onboard NIC in your BIOS.
 
Or you can go to Settings -> Network Settings -> Interface rules and adjust so that the 10GB nic is eth0
 
Either way, note that when your server reboots it will get a different IP address from the router since the 10GB nic has a different mac address. It might help to have a monitor on the server so you can see the ip address on the console when the system boots.

You have a myunraid.net certificate, which uses URLs in the format:
  https://[ip-address].[hash].myunraid.net
 
If eth0 does not have an IP address, nginx is unable to start because it can't generate a server name for that URL. So we see this in your syslog:
May 29 00:47:53 Talonhawk root: Starting Nginx server daemon... May 29 00:47:53 Talonhawk root: nginx: [emerg] invalid number of arguments in "server_name" directive in /etc/nginx/conf.d/servers.conf:63  
For now, please make sure eth0 has an IP address.
 
This shortcoming will be addressed in 6.12.

You have configured Unraid to use port 84 for both http and https traffic, this will not work. They need to be on different ports.
 
The defaults are:
  HTTP port:   80
  HTTPS port:  443
 
The only reason to change the defaults is if you want to run Docker containers on those ports.
 
On your flash drive there is a config/ident.cfg file. Edit that and change these entries so that they are unique on the system and do not conflict with any Docker containers:
PORT="84" PORTSSL="84"  
After doing that, run:
/etc/rc.d/rc.nginx reload Or restart the server

No, the OS reports the IPv6 link but the back end isn't in place to support it yet.

It appears that something on your network is preventing the server from downloading this file:
  https://sfo2.digitaloceanspaces.com/unraid-dl/unraid-api/dynamix.unraid.net.plg
 
You can manually backup the flash drive by going to Main -> Boot Device -> Flash -> Flash Backup

You need to migrate from the legacy unriad.net certificate to the new myunraid.net certificate. See https://unraid.net/blog/ssl-certificate-update-2

If UPnP is enabled on your router, you might as well use it. If you have disabled UPnP in your router because you think your router's implementation has security issues then I'm not going to argue with you.
 
There are several benefits to UPnP here:
You don't have manually configure your router to do port forwarding, so it is easier In "Static - UPnP" mode, the system picks a new random WAN port every time you reboot the server.  In "Dynamic - UPnP" mode, it picks a new random WAN port every time Remote Access is enabled from Connect. And the wan port is fully closed when remote access is disabled from the Connect side. So assuming you trust your router's implementation of UPnP, then "Dynamic - UPnP" is the best option to choose. 
 
If you don't trust your router's implementation of UPnP then I would choose "Dynamic - Manual Port Forward"
 
For more information about Remote Access please see https://wiki.unraid.net/Connect#Remote_Access_.28optional.29

It looks like your server is configured for Jumbo frames, revert that back to normal. See https://forums.unraid.net/topic/120220-fix-common-problems-more-information/page/2/#comment-1167702
 
 
It also looks like the server has four NICs, but eth0 is not connected. Unraid works best when eth0 is your main NIC, you can either move the network cable around until you find eth0 or you can go to Settings -> Network Settings Interface Rules and adjust until the connected NIC is eth0. See https://forums.unraid.net/topic/120220-fix-common-problems-more-information/page/2/#comment-1170361
 
Once the network is back, I highly recommend you install the Fix Common Problems plugin as it will automatically alert you to this sort of thing.
 

It sounds like a DNS issue. Go to Settings -> Network Settings, delete any DNS servers listed and replace with 8.8.8.8
 
If you continue to have issues, be sure to upload your full diagnostics.zip file (from Tools -> Diagnostics)

You need to access the My Servers dashboard from a remote location, then it will show the Remote Access url instead of the Local Access url.

On Settings -> Management Access be sure to set the "Local TLD" to "local", this will activate mDNS. Note that mDNS only works if your server and client are on the same subnet. If you still have issues you might need to research mDNS and see if something on your network is blocking it.

Please see https://wiki.unraid.net/My_Servers#How_to_access_your_server_when_DNS_is_down

It looks like you are using an unraid.net url, but something has changed on your network to enable "DNS Rebinding Protection". The culprits are likely a setting in your router, or some security software running on your client, or the DNS server used on your client.
 
Follow the instructions here to get access to your server's webgui again:
  https://wiki.unraid.net/My_Servers#How_to_access_your_server_when_DNS_is_down

Sorry for the trouble. I am aware of two systems that are getting this "toLowerCase" problem, we are still tracking it down. It will take a plugin update to resolve, if this is causing issues for you, you might want to uninstall the My Servers plugin for now.

It appears to be configured correctly, perhaps you have the wrong url? 
 
I'd suggest that when you are aware from your house, access the My Servers dashboard:
  https://forums.unraid.net/my-servers/
If you are not on the same network as the server, it will show a "Remote Access" link which you can click to access your server.