Support - Dashboard mod 504 timeout

LSIO Discussion Container Support
1

Hi,

I recently migrated my server to a new system with Unraid.
It works fine, all drives mount everything boots.

However, a new IP was assigned to my system due to the new NIC.
I updated all my systems, but ever since then, the Dashboard mod hasn’t loaded.

I’m not willing to move everything back to the old network IP.
I’ve tried uninstalling/reinstalling the dashboard mod and it has the same issue.
Is there a config for the Dashboard mod that I can check?

2

LinuxServer.io Support
Please could you provide the following information so we can help with supporting your issue:

  • OS/docker info (ex: Ubuntu 20.04, Docker 20.10)
  • Hardware (ex: Dell R730, VM, Raspberry Pi 3b, Synology DS916+)
  • Docker command or compose snippet
  • Container logs (Please use hastebin to post these)
  • Describe the issue you’re having with the container.

Mind the #rules and remember this server supports the containers, not the apps inside (they have their own support).

3

Hi, apologies for the delay.

  • OS/docker info (ex: Ubuntu 20.04, Docker 20.10)
    Unraid 6.12.4/Docker 20.10.24
  • Hardware (ex: Dell R730, VM, Raspberry Pi 3b, Synology DS916+)
    Dell R720
  • Docker command or compose snippet
    Not quite sure how to get this for you. Here’s my template:
    Docker - template - Pastebin.com
  • Container logs (Please use hastebin to post these)
    SWAG Log - Pastebin.com
  • Describe the issue you’re having with the container.
    When attempting to open SWAG’s dashboard ([IP]:81) it gives a 504 timeout error
4

can you check the out of date entry mentioned in your logs, restart swag, and test? if it still doesn’t work, please post updated logs? I will mention this thread to the teammember that handles dashboard.

5

Another thing to try is moving away /config/log/nginx/access.log and restarting swag, if that works then check the size of the old access.log, it may have timed out trying to read it.

1 Like
6

Figured out what was causing it.
The crowdsec bouncer is blocking it.

made a whitelist as here:

7

This topic was automatically closed 5 days after the last reply. New replies are no longer allowed.