moosedookie

Members
  • Posts

    9
  • Joined

  • Last visited

Posts posted by moosedookie

  1. 3 hours ago, ljm42 said:

    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

    Updating to v6.12.1 fixed it for me. Everything is working as intended now. 😁

     

    Thank you so much for working through this with me and finding a solution so quickly!

    • Like 1
  2. 2 hours ago, ljm42 said:

     

    Thanks for the diagnostics.

     

    Please open a web terminal SSH to the server, or connect a keyboard and monitor and run this, then copy/paste the results back here:

    cat /etc/nginx/conf.d/servers.conf

     

    root@MOOSE-SERVER:~# cat /etc/nginx/conf.d/servers.conf
    #
    # Listen on local socket for nchan publishers
    #
    server {
        listen unix:/var/run/nginx.socket default_server;
        location ~ /pub/(.*)$ {
            nchan_publisher;
            nchan_channel_id "$1";
            nchan_message_buffer_length $arg_buffer_length;
        }
        location ~ /nchan_stub_status$ {
            nchan_stub_status;
        }
    }
    #
    # Always accept http requests from localhost
    # ex: http://localhost
    # ex: http://127.0.0.1
    # ex: http://[::1]
    #
    server {
        listen 127.0.0.1:80; # lo
        listen 127.0.0.1:14443; # lo
        listen [::1]:80; # lo
        listen [::1]:14443; # lo
        #
        include /etc/nginx/conf.d/locations.conf;
    }
    #
    # Redirect http requests to https
    # ex: http://tower.local -> https://lan-ip.hash.myunraid.net
    # ex: http://192.168.1.100 -> https://lan-ip.hash.myunraid.net
    #
    server {
        listen 10.253.0.1:80 default_server; # wg0
        return 302 https://10-253-0-1.hash.myunraid.net:14443$request_uri;
    }
    #
    # Redirect http requests to https
    # ex: http://[::ffff:192.168.1.100] -> https://lan-ip.hash.myunraid.net
    #
    
    #
    # Return 404 (Not Found) as default ssl action, using self-signed cert
    #
    server {
        listen 10.253.0.1:14443 ssl http2 default_server; # wg0
        # Ok to use concatenated pem files; nginx will do the right thing.
        ssl_certificate         /boot/config/ssl/certs/MOOSE-SERVER_unraid_bundle.pem;
        ssl_certificate_key     /boot/config/ssl/certs/MOOSE-SERVER_unraid_bundle.pem;
        ssl_trusted_certificate /boot/config/ssl/certs/MOOSE-SERVER_unraid_bundle.pem;
        #
        # OCSP stapling
        ssl_stapling off;
        ssl_stapling_verify off;
        return 404;
    }
    #
    # Port settings for https using CA-signed cert
    # ex: https://lan-ip.hash.myunraid.net
    # ex: https://hash.unraid.net
    #
    server {
        listen 10.253.0.1:14443 ssl http2; # wg0
        server_name 192-168-33-134.hash.myunraid.net 2600-6c40-2d7f-7cc0-215-17ff-fee8-934c.hash.myunraid.net [wanip].hash.myunraid.net 2600-6c40-2d7f-7cc0-215-17ff-fee8-934c.hash.myunraid.net 10-253-0-1.hash.myunraid.net;
        # Ok to use concatenated pem files; nginx will do the right thing.
        ssl_certificate         /boot/config/ssl/certs/certificate_bundle.pem;
        ssl_certificate_key     /boot/config/ssl/certs/certificate_bundle.pem;
        ssl_trusted_certificate /boot/config/ssl/certs/certificate_bundle.pem;
        #
        # OCSP stapling
        ssl_stapling on;
        ssl_stapling_verify on;
        #
        location ~ /wsproxy/14443/ { return 403; }
        include /etc/nginx/conf.d/locations.conf;
    }

     

  3. 9 hours ago, JorgeB said:

    Try booting in safe mode to rule out any plugin issues.

    Thanks for the quick reply!

    When I first tried to boot into GUI safe mode I was just getting a black screen with a flashing cursor in the top left corner. I uninstalled the nvidia driver and rebooted to GUI safe mode and was able to login but I am still having the same issue...

  4. Hello,


    I recently upgraded from v6.11.5 to v6.12.0 and am now unable to connect to the webUI from other systems.

    If I boot unraid in GUI mode it can access the UI from the unraid server but not from other systems.

    I get "This site can't be reached" "ERR_CONNECTION_REFUSED" in chrome and just get "Unable to connect" in Firefox.

    I decided to use the unraid connect port check to see if it can connect but get "The Unraid server is unreachable from outside your network.".


    I've also noticed that I am no longer able to access anything over SMB anymore since the update.

    I'm not sure what is going on, any help would be appreciated.

     

    Thanks.

    moose-server-diagnostics-20230616-0016.zip

  5. 5 minutes ago, ljm42 said:

     

    Thanks for the offer! I'm 98% sure I know what is going on here so it shouldn't be needed. It should be fairly tough to trigger this bug so hopefully not a lot of people hit it.

     

    We just released an updated plugin that masks the underlying problem so nobody else will get to see the webgui completely breaking like that. Apologies to the people who did "get" to see it. 

     

    I expect we'll have another plugin update later today that fully fixes the underlying problem. In the meantime a small number of (un)lucky folks might get signed out of Unraid.net after upgrading, and possibly have trouble signing back in. The next fix will resolve that.

    Awesome, thanks for the quick fix. I figured you wouldn't need it but offered just in case.

    Thanks again, I appreciate your hard work!

    • Like 1
  6. 4 hours ago, ljm42 said:

     

    I can reproduce this if I purposefully corrupt the config file, so we've got a fix on the way.

     

    In the meantime if anyone else runs into this you can get past it by deleting this file from your flash drive:

        /boot/config/plugins/dynamix.my.servers/myservers.cfg

     

    If someone with the problem wouldn't mind PMing me a copy of the file before you delete it, it might give us an idea of how the file is being corrupted. Don't post it here though, it has sensitive info.

    I was having this same issue. I deleted the myservers.cfg and now I'm back in business. Thanks! If you need a copy of myservers.cfg pre deletion I can send it to you.