Jump to content

ljm42

Administrators
  • Posts

    4,404
  • Joined

  • Last visited

  • Days Won

    27

Posts posted by ljm42

  1. 3 hours ago, floepie05 said:

    No, upload, as in from the server to LAN/internet.  This is too slow @ 35 MB (iperf/speedtests/SMB transfers).  LAN to server is fast and expected.

    Yes, nvme drive as cache.

     

    As I mentioned above, moving the MTU from 1500 to 9000 almost doubles the upload speed, still not the full gig.  So, likely something wonky with the driver or adapter or unraid, not sure.

     

    This is extremely confusing.

     

    There are no advantages to using jumbo frames on one computer, you have to use them on every computer that that computer might talk to. Typically this is not practical unless you have a multiple nics and a separate subnet that key systems use to talk. But the main network should be kept at 1500.

     

    Have you changed the MTU on your router? That could explain what you are seeing. If so, return the router's MTU to 1500

  2. Jumbo frames are evil. Well, they cause a lot of problems anyway. Fix Common Problems will warn against them:

    https://forums.unraid.net/topic/120220-fix-common-problems-more-information/page/2/#comment-1167702

     

    To manually remove them, on the flash drive, edit config/network.cfg. Find any MTU[x] entries and change them to "1500", i.e.:

    MTU[0]="1500"
    MTU[1]="1500"
    

    When you reboot you will be back to stock MTUs.

    • Upvote 1
  3. 22 hours ago, sunbear said:

    Active Backup seems to be the only thing that works without errors and without a managed switch.

     

    Right, all the fancy bonding options require the NICs to be connected to a network switch that is configured with the same settings.

     

     

    22 hours ago, sunbear said:

    While someone knowledgeable is here, would you also happen to know how to get rid of the following message?

     

    it sounds like something is trying to send mail but mail isn't configured. You can do that at Settings -> Notification Settings -> SMTP Settings

  4. 3 hours ago, singularity098 said:

    Ok, I've got you.  Sharing my diagnostics here.

     

    So it looks like you followed a guide somewhere and added 27 lines of code to the config/go script on your flash drive. This code modifies two core Unraid fails:

    • /etc/rc.d/rc.docker
    • /usr/local/emhttp/plugins/dynamix/scripts/monitor

    I strongly recommend removing all that and restoring your go script to stock:

    #!/bin/bash
    # Start the Management Utility
    /usr/local/sbin/emhttp &

    then rebooting. This will get you back into a supported configuration.

     

    If you are unwilling to return to stock Unraid, you should find where you originally got the code and see if there is an updated version. Keep in mind that with every Unraid update there is a chance this code will break so you should bookmark the source and check it regularly for updates.   Modifying core Unraid files like this is highly discouraged, always be sure to upload your diagnostics when asking questions so the people helping you know up front about the mod. Any support questions about the mod or the files it modifies should be asked in the thread where you got the mod.

  5. Navigate to Settings -> Network Settings and change your bond type to "active backup", see if that makes the errors go away.

     

    I'd recommend reviewing the warnings from Fix Common Problems, it has probably been warning about this but the specifics are not being logged:

    root: Fix Common Problems: Ignored errors / warnings / other comments found, but not logged per user settings

     

    There is more info about complex bonds here:

    https://forums.unraid.net/topic/120220-fix-common-problems-more-information/page/2/#comment-1100015

     

  6. To be safe, make a backup of your flash drive first. Main -> Boot -> Flash -> Flash Device Settings -> Flash Backup

     

    The files are stored on the flash drive in the config/wireguard directory. Delete everything in that directory (but leave the directory itself) to start over with WireGuard.

     

    To do this from the web terminal type:

    rm -r /boot/config/wireguard/*

    ( Be extremely careful typing that command! A space in the wrong place will wreak havoc. )

    • Like 1
  7. 2 hours ago, singularity098 said:

    No, I don't know where the script comes from.

     

    Obviously it has something to do with a Dynamix plugin based on the file path, but I had uninstalled all Dynamix plugins and the thing was still there and writing errors to my log.  I have no idea where the script comes from or what the purpose is.  All I know is that I noticed the error in the log, Googled it, ended up in this thread and found a fix.

     

    The code being discussed in this thread is not stock Unraid. Something has completely overwritten this file: /usr/local/emhttp/plugins/dynamix/scripts/monitor. I'm guessing that you added code to your /boot/config/go script but without diagnostics it is hard to tell. Please upload your diagnostics.zip (from Tools -> Diagnostics)

  8. 4 hours ago, singularity098 said:

    I was able to fix it on my system.  Even though on my system, the script "/usr/local/emhttp/plugins/dynamix/scripts/monitor" does NOT have single or double quotes as shared by others:

     

    if ( ! ((date(i) * date(H) * 60 + date(i)) % $sync_interval_minutes) && file_exists("/var/lib/docker/containers")) {

     

    I changed it to adding double quotes around those variables anyway.  It fixed the issue:

     

    if ( ! ((date("i") * date("H") * 60 + date("i")) % $sync_interval_minutes) && file_exists("/var/lib/docker/containers")) {

     

    No more errors in my logs.

     

    This is not stock Unraid code, but was due to a modification you added to your go script right? Please make that clear when requesting help, and upload your diagnostics so people can see the code you added to your go script.

     

    Overall though, I'd recommend discussing this in the thread where you got the code, perhaps there has been an update. Or you can delete all the mods to the go script and return to stock Unraid.

  9. Hey @EldonMcGuinness, got another one for you :)  I am seeing this PHP warning show up in my log:

     

    [07-May-2024 17:15:01 America/Phoenix] PHP Warning:  Undefined array key "type" in /usr/local/emhttp/plugins/DriveStandbyMonitor/includes/page.php on line 47

     

    Even though it is just a warning, we try to clean these sorts of things up.

     

    To see these warnings, go to Tools -> PHP Settings and enable "All Categories".  Then press View Log.  As you interact with the server you will see any PHP errors or warning in the log.

  10. @EldonMcGuinness please add this file to the plugin to stop Unraid Connect from backing up monitor.db every 15 minutes:

    echo "monitor.db" > /boot/config/plugins/DriveStandbyMonitor/.gitignore

     

    Here is an example of how the rclone plugin distributes a similar file:
    https://github.com/Waseh/rclone-unraid/blob/6ed5f0ecf8cf1077795ecf7831aa84fd54408096/plugin/rclone.plg#L241 

     

    Note: initially this will only take effect on new plugin installs. The next release of the Connect plugin will make sure existing systems obey that .gitignore file too, without anyone having to do anything at the command line.

     

    This does mean that Unraid Connect Flash Backup will stop backing up this file. If you think it should be backed up occasionally, you could have the plugin copy it to a new file name perhaps once a day or once every few days.  The main goal here is to avoid the write amplifications that flash backup causes when this file changes every 15 minutes.

  11. Flash backup runs whenever it detects a change on the flash drive, so something is updating a file on your flash drive every 15 minutes.

     

    To see what it is, open a web terminal and type:

    cd /boot

    then

    git log --stat

    You can up/down arrow through the list, press Q to quit

     

    You will probably see the same file being mentioned multiple times, please copy/paste what you see back here.

    • Like 3
  12. On 4/27/2024 at 4:14 PM, jeffreywhunter said:

    I've also made sure that Enable DNS Rebind protection is turned on in my router.

     

    This is the problem, DNS Rebind Protection needs to be disabled.

     

    Diagnostics shows that DNS requests for 192-168-4-100.hash.myunraid.net do not resolve.  It needs to resolve to 192.168.4.100 in order for the url to work.

     

    Isn't there a message about this on the Settings -> Management Access page?

    • Upvote 1
  13. 1 hour ago, jeffreywhunter said:

    None of the links on the Management access page works except the local NAT server address.  I've tried them all and only the NAT address works from a local browser (warning about not secure).

     

    Please right click on the https://ip.hash.unraid.net one and choose "open in a new tab". Please show a screenshot of what happens.

     

    1 hour ago, jeffreywhunter said:

    not trying explicitly to do anything other than clicking on the command line icon in the unraid menu to open a terminal session.

     

    A screenshot of this would be helpful too

     

  14.  

    On 4/28/2024 at 9:59 AM, jeffreywhunter said:

    Quick update, today I discovered that I can ONLY access my server through connect.unraid.net website.  If I use https://192-X-X-X.[that special custom string].myunraid.net/Dashboard it will not work now.  I can only access if I login to connect.myunraid.net.  I must have missed something important...

     

    Something must be wrong with your bookmark, maybe the server's IP address changed?

     

    Access the webgui through Connect and go to the Settings -> Management Access page. That will list all of the available local access urls, including the ip.hash.myunraid.net one. When you use the url listed there you should be able to access the server.

     

    On 4/27/2024 at 4:14 PM, jeffreywhunter said:

    I'm not not able to access a terminal session/command line from the WebUI menu any longer.  When i click, I get the following: 

    --------------

    "serverip":4200

    This site can’t provide a secure connection

    "ServerIP" sent an invalid response.

     

    ERR_SSL_PROTOCOL_ERROR

     

    I need more detail about what you are doing. Based on the settings you provided, your webgui is hosted on port 443 not 4200.  Are you maybe trying to do something with a Docker container?

     

    Also please provide the full diagnostics.zip (from Tools -> Diagnostics)

  15. When the problem is occurring, please SSH in and run:

    /etc/rc.d/rc.nginx restart

    What is the response, and does it help?

     

    Also please run:

    cat /var/log/nginx/error.log

    and copy/paste the results back here. There is a lot of noise in this file but maybe something useful.

  16. On 4/20/2024 at 1:06 AM, Interstellar said:

    Anyone else having issues where the UnRAID GUI stops working?

    The login page pops up, I enter user/pass as normal, click login then... nothing, just hangs in both Safari and Chrome.

    Tried /etc/rc.d/rc.nginx reload - no change.

     

    As far as I can tell the server itself is working normally, SSH works, dockers/VMs are all running.

    Absolutely nothing in the logs relating to nginx at all.

     

    Uptime was since a day or two after .10 was released and I'm using macvlan already.

    Anyone else?

     

    Please start a new thread in General Support, include as much detail as you can along with your diagnistics.zip (can get from SSH by typing "diagnostics", any questions go ahead and ask in your new thread to avoid a lot of back and forth in this announce post)

  17. On 4/12/2024 at 7:27 PM, karash said:

    It looks like the "*.myunraid.net" is using certificate_bundle.pem while the local URLs are all using the SERVER_unraid_bundle.pem certificate, this is causing me to get an SSL warning when I navigate to my Unraid GUI.

     

    This is correct.  The certificate_bundle.pem cert is ONLY valid for *.myunraid.net urls. There is zero benefit to using it with other urls.  If you access the server by IP address or by name then it will use a self-signed cert.

     

    On 4/12/2024 at 7:27 PM, karash said:

    But there are no instructions on setting that up.

     

    It is fully setup. To use it, click the url starting with https://192-168... that you blanked out of the screenshot.

     

    For more information, see https://docs.unraid.net/unraid-os/manual/security/secure-webgui-ssl/

×
×
  • Create New...