504 Gateway time-out when try to open workbench after intallation on Debian

SirIcy · Nov 10th 2025

When I try to open workbench from a fresh installation on Debian 13 error "504 Gateway time-out" comes up.

SSH access works fine.

Browser cache refresh didn't help.

Root has sufficient space: /dev/sda6 411G 2.5G 388G 1% /

Hardware is Soyo M4 Pro

votdev · Nov 10th 2025

OMV7 requires Debian 12. OMV8 which is using Debian13 is currently in development, not mentioned everywhere and therefore not supported atm.

SirIcy · Nov 10th 2025

Thx!

I followed the guide here: https://docs.openmediavault.or…stallation/on_debian.html

First sentence of this guide is: "You can install openmediavault on an existing Debian 13 installation as well."

ryecoaaron · Nov 10th 2025

Quote from SirIcy

First sentence of this guide is: "You can install openmediavault on an existing Debian 13 installation as well."

The page pops up a note in the corner that says it is a dev version.

votdev · Nov 10th 2025

If you open https://docs.openmediavault.org/, then it points you to the stable version. Using latest points you to the development version.

pepsov · Thursday, 1:44 am

OK, is there a way to log into the Web UI or not?
Nobody's interested in smart remarks that the system is still in DEV.
DEV systems also allow login - when properly designed.

I am with the OP on this - if there is a recommended way of doing things, and that way does not work, users can request for help/assistance/instructions.

It was hard enough to install the dev OMV8 on top of Trixie. Tell us what's wrong with the UI, and if we can use it or not.
If the answer is NO then we will give up on it and go back to OMV7.

We are trying to help you here, by being the guinea pigs. Some respect, please!

ryecoaaron · Thursday, 12:55 pm

Quote from pepsov

is there a way to log into the Web UI or not?

Yes but not without output from what you have attempted already. I highly recommend running the install script as it will install omv8 on debian13.

Quote from pepsov

Nobody's interested in smart remarks that the system is still in DEV.

Chill out. No one is posted smart remarks. This thread happened before the official beta period. We didn't recommend installing omv 8 at that time.

Quote from pepsov

DEV systems also allow login - when properly designed.

omv 8 has hardly changed. It is not a design problem.

Quote from pepsov

We are trying to help you here, by being the guinea pigs. Some respect, please!

That goes both ways. The OP likely was trying to install Debian 13 and OMV 7 before the beta. If you are still having issues, I think a new thread is appropriate.

pepsov · Thursday, 1:32 pm

The symptoms are as described in the OP:
When opening the WebUI after installing OMV8 on top of Debian 13, following the recipe posted here:

Thread

Install OMV8 on Debian 13 (Trixie)

!!! ATTENTION !!!

OMV8 is in beta phase right now. You can give it a try, but you should not use it on production systems.
The only supported platforms are AMD64 and ARM64.
If there are database changes, there will be no automatic migrations between 8.0-x versions.

!!! ATTENTION !!!

Please refer to https://docs.openmediavault.or…stallation/on_debian.html for a detailed description.

To install OMV8 on an already installed Debian 13 (Trixie), simply execute the following steps as root user:

(Code, 11…

votdev

Nov 13th 2025

one gets a long wait and then: "504 Gateway time-out"

Nothing is shown in system logs (`dmesg -w` running in an SSH session), nor in auth.log, so it's clearly not a question of authentication.

(btw, providing the wrong credentials results in a proper message about that fact in the UI)

ryecoaaron · Thursday, 2:23 pm

Quote from pepsov

The symptoms are as described in the OP:
When opening the WebUI after installing OMV8 on top of Debian 13, following the recipe posted here: Thread Install OMV8 on Debian 13 (Trixie) !!!
one gets a long wait and then: "504 Gateway time-out"

I understand. A 504 error can be caused by many things. The OP hasn't been back in weeks. That is why I suggested a new thread.

Quote from pepsov

Nothing is shown in system logs (`dmesg -w` running in an SSH session), nor in auth.log, so it's clearly not a question of authentication.
(btw, providing the wrong credentials results in a proper message about that fact in the UI)

Without the output from the install, it is hard to say what went wrong. The install thread you link to is a VERY minimal install. That is why I have spent so much time maintaining the install script for years. It avoids a lot of the common issues.

Post the output of:

dpkg -l | grep openme

sudo omv-salt deploy run nginx phpfpm

pepsov · Thursday, 2:53 pm

I'll try that and will post the output.
Meanwhile - what are the best logs to check/monitor for OMV-specific messages? (sorry - not much OMV debugging experience)

ryecoaaron · Thursday, 2:56 pm

/var/log/php8.4-fpm.log

/var/log/nginx/openmediavault*

journalctl

The thing I do the most but I don't think you need it at this point is put omv-engined in debug mode:

monit stop omv-engined

omv-engined -df

pepsov · Thursday, 6:54 pm

systemctl restart postfix

- that's what fixed the issue with WebUI '504 tomeout'

BTW - that was already mentioned in another Forum post:
No login to OMV-Workbench after fresh install on Debian 13

votdev · Thursday, 7:06 pm

Quote from pepsov

systemctl restart postfix

- that's what fixed the issue with WebUI '504 tomeout'

BTW - that was already mentioned in another Forum post:
No login to OMV-Workbench after fresh install on Debian 13

That is really strange. I do not see any connection between an erroneous postfix and a non functional nginx or phpfpm.

pepsov · Thursday, 7:50 pm

Well, that's exactly what I did, and I paid extra attention to NOT do anything else along the way.

1. SSH into the machine as root;
2. Tried to log in via WebUI, and got the "504 Gateway time-out"

3. In the SSH session did `systemctl status postfix` - it showed status "inactive (dead)":

$ ssh -Y root@192.168.1.53
root@192.168.1.53's password:
Linux omv8 6.12.57+deb13-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.12.57-1 (2025-11-05) x86_64

The programs included with the Debian GNU/Linux system are free software; the exact distribution terms for each program are described in the individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law.

Last login: Wed Dec 3 20:07:17 2025 from 192.168.1.12

root@omv8:~# systemctl status postfix
○ postfix.service - Postfix Mail Transport Agent (main/default instance)
Loaded: loaded (/usr/lib/systemd/system/postfix.service; disabled; preset: enabled)
Active: inactive (dead)
Docs: man:postfix(1)

root@omv8:~# systemctl restart postfix

4. Tried again to log in via WebUI, and got in!

Could it be that postfix restarts some other service along the way?

pepsov · Thursday, 7:52 pm

The really funny thing is that now, when WebUI login works, postfix service is once again dead, but this does not affect the WebUI logins.
I agree with you - that's strange!
But at least works

votdev · Thursday, 8:12 pm

After doing some research, I found out that a malfunctioning postfix can actually block the mail command in PHP and thus trigger the 504 error. And yes, an email is sent during login if certain conditions are met.

votdev · Thursday, 9:28 pm

The issue will hopefully be fixed with https://github.com/openmediava…3bbcb351a86c120815177e339 in openmediavault 8.0-11.

504 Gateway time-out when try to open workbench after intallation on Debian

votdev Nov 10th 2025

votdev Thursday, 9:29 pm

Participate now!