May 29, 20233 yr I am unable to access Unraid via GUI even directly connected to the server. when I log into the server I get a unable to connect page. This happened after I removed a 5700xt and installed a much older card for server access and a Intel arc A770. All of the docker containers appear to be working fine and I have terminal access. I do not know how to pull a log file via terminal, and did not get any links on how to on a search. I thought perhaps my issue was a DNS problem and that is why I tried to access the GUI directly from the server. I assume that would bypass any DNS problems. I did change the default ports on the server to 4080 and 40443. Thinking that may have been part of the issue I shutdown the server went on the boot usb and changed it back to 80 and 443. I did ifconfig and both of the networks on the server are connected have an ip address and are transmitting and receiving. The old graphic card that I have in there is a R7950 (the 2012 release not the current one), It is the card that I had when I built my first unraid server 6-10 years ago, I assumed it would be fine for GUI access on the server. I am not sure what else to try any help would be appreciated.
May 30, 20233 yr When signed in at the terminal, type `diagnostics` and note where it stores the zip file on your flash drive. Then attach that file to your next post here.
May 30, 20233 yr Author talonhawk-diagnostics-20230530-1248.zip thanks here is the diagnostics file. I found a couple of other posts similar in nature and tried the use_ssl no command and it did not work.
May 30, 20233 yr Author I am Not sure what happened but after I uploaded the diagnostics my eth0 changed to the same network as my eth1 and the GUI started working. I am Going to assume it is some sort of network issue and try to Iron it out. Out of curiosity say my network is down for whatever reason should Unraid be able to boot into GUI ?
May 30, 20233 yr Solution 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.
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.