Jump to content

  • 6.12 webui is not starting

    Nischi

    By Nischi

      • Solved

    I went from 6.11.5 ro 6.12.0 a few days ago (before the 6.12.1 hit).

    Now my webui won't start, not remotely nor on localhost.

    I tried to restore from a backup to a new usb-stick.

    I also run my router inside a VM on this machine, where i passthrough a NIC.

     

    I'm not sure what is wrong.

    Any ideas from someone?

     

    from what I can glance, this might be relevant?

     

    Quote

    Jun 22 16:17:46 changeme emhttpd: shcmd (35): /etc/rc.d/rc.nginx start
    Jun 22 16:17:46 changeme root: Starting Nginx server daemon...
    Jun 22 16:17:57 changeme nginx: 2023/06/22 16:17:46 [emerg] 2081#2081: bind() to [::1]:80 failed (99: Cannot assign requested address)
    Jun 22 16:17:59 changeme dbus-daemon[2112]: [session uid=0 pid=2110] Activating service name='org.a11y.Bus' requested by ':1.2' (uid=0 pid=2415 comm="sakura")
    Jun 22 16:17:59 changeme dbus-daemon[2112]: [session uid=0 pid=2110] Successfully activated service 'org.a11y.Bus'
    Jun 22 16:18:00 changeme emhttpd: cmdStart: no registration key

     

    changeme-diagnostics-20230622-1618.zip

    Go to reports Stable Releases

    User Feedback

    Recommended Comments

    bonienl

    You have a port conflict, nginx can not start because port 80 is already used by something else.

    Start in safemode and resolve the conflict.

     

    Link to comment
    Nischi

    wow that was fast. Thanks

     

    Okay, will try that, not sure what suddenly got port 80 after an upgrade.

    Maybe the most easy way to resolve for now might be to change unraid's port number instead.

    Link to comment
    bonienl

    To resolve the conflict, there are multiple ways to do so.

    When changing GUI ports, make sure the new port assignments do not conflict with other running services. This means choose port numbers higher than 1024.
     

    Link to comment
    Nischi

    Tried changing the port to 10081 and 12081, still seems to be the same issue. might it be something else?

     

    Is there some way to revert to older version without GUI, maybe with CLI?

     

    Also I'm a bit confused as the version says 6.1.33. thought it would have said 6.12.0

     

    See newly attached diagnostics.

    unraid-diagnostics-20230622-1820.zip

    Edited by Nischi
    Link to comment
    Nischi

    Thanks again. I will first try to revert back to 6.11.5 to see if that works, otherwise I guess I have to wait for 6.12.2.

    Also I just realized that 6.1.33 of course is the kernel version not the unraid version.

    Link to comment
    bonienl

    I see what is happening. Problem is not the port (you may make it default again)

    Remove the following lines from your 'go' file and restart the system

      

    #nischi completely disable ipv6 on unraid
sysctl net.ipv6.conf.all.disable_ipv6=1
sysctl net.ipv6.conf.default.disable_ipv6=1

     

    • Like 1
    Link to comment
    Nischi

    Seems like those lines in the go file  were the culprit.

     

    I'm not sure why, maybe because I restored from my backup or maybe because of the update 6.12.1. But all my plug-ins got uninstalled. Had to reinstall all of them.  But now it's in working order again. 

     

    Thanks for the help!

    Link to comment


    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.

    Guest
    Add a comment...

    ×   Pasted as rich text.   Restore formatting

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.

    ×

  • Status Definitions

     

    Open = Under consideration.

     

    Solved = The issue has been resolved.

     

    Solved version = The issue has been resolved in the indicated release version.

     

    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.

     

    Retest = Please retest in latest release.

    Priority Definitions

     

    Minor = Something not working correctly.

     

    Urgent = Server crash, data loss, or other showstopper.

     

    Annoyance = Doesn't affect functionality but should be fixed.

     

    Other = Announcement or other non-issue.

×
×
  • Create New...