Page 1 of 1
[SOLVED] HTTP/1.1 504 Gateway Time-out
Published: February 25, 2019 - 4:48 PM
by mohasdis
Hello everyone,
Since the update from version 1.5 to 1.7.
I get the nice message below when I open my console.
I saw a similar topic on the forum (
[RESOLVED] nginx 504 gateway timeout when upgrading to 1.7).
I did the same as @olivetree.
Shutting down services properly:
Code: Select all
net stop WAPTService
net stop WAPTServer
net stop WAPTNginx
net stop WAPTPostgresql
Launch the installation via the local admin account.
But still nothing.
I also launched a
Minimal Catering But nothing I do works, I still get the same message.
Does anyone have any ideas?
Thank you for your help
Re: HTTP/1.1 504 Gateway Timeout
Published: February 26, 2019 - 12:11 PM
by beryl
Hello
, unfortunately, I have no idea. However, I just did an update like you (1.5 -> 1.7) and I have the joy of getting the same message.
On the other hand, my "WAPTServer" service is "Paused", and for the moment I can't get it to resume.
Re: HTTP/1.1 504 Gateway Timeout
Published: February 26, 2019 - 2:16 PM
by mohasdis
Hello @beryl
You tried the command:
A complete server restart?
Re: HTTP/1.1 504 Gateway Timeout
Published: February 26, 2019 - 2:24 PM
by beryl
Yes, I performed a complete machine restart.
The service remains paused.
Re: HTTP/1.1 504 Gateway Timeout
Published: February 26, 2019 - 10:29 PM
by sfonteneau
Could you try this:
viewtopic.php?f=13&t=1481&p=4973&hilit=sc+delete#p4973
If this is indeed the problem, it's certainly because we can't delete the waptserver service if it exists, but since the path no longer exists, we need to delete it...
Re: HTTP/1.1 504 Gateway Timeout
Published: February 27, 2019 - 09:22
by Alesk
Hello everyone,
I have exactly the same problem with a migration from 1.5 to 1.7 in admin mode. Local
Log error.log from nginx
2019/02/26 18:42:24 [error] 2488#1920: *1 upstream timed out (10060: FormatMessage() error:(15100)) while connecting to upstream, client: 192.168.0.158, server: _, request: "GET /favicon.ico HTTP/1.1", upstream: "
http://127.0.0.1:8080/favicon.ico", host: "wapt.XXX.XXX.local"
WAPT service paused and unable to restart.
Error 504 Gateway Timeout for accessing the web URL from the server or from a workstation.
Error 504 Gateway Timeout for accessing the console.
Fortunately, I have a snapshot. Before installation, I reverted to version 1.5 to maintain production.
I performed an intermediate migration from 1.5 to 1.6, and the result is the same.
Do you have any ideas?
Thank you.
Re: HTTP/1.1 504 Gateway Timeout
Published: February 27, 2019 - 10:22 AM
by mohasdis
Thank you @sfonteneau, I finally succeeded!
I did as in the thread you linked to:
1/
Code: Select all
net stop waptserver
net stop waptservice
net stop waptnginx
sc delete waptserver
2/ I launch my update as a local admin.
3/
Code: Select all
c:\wapt\waptpython.exe c:\wapt\waptserver\winsetup.py -ldebug install_waptserver -c c:\wapt\conf\waptserver.ini
Works for me from 1.5 to 1.7
Re: HTTP/1.1 504 Gateway Timeout
Published: February 27, 2019 - 10:53 AM
by beryl
Perfect, same as @mohasdis
Code: Select all
net stop waptserver
net stop waptservice
net stop waptnginx
sc delete waptserver
reboot server
Code: Select all
net stop waptservice
net stop waptnginx
Running waptserversetup.exe as administrator on a local Admin session.
Code: Select all
c:\wapt\waptpython.exe c:\wapt\waptserver\winsetup.py -ldebug install_waptserver -c c:\wapt\conf\waptserver.ini
A huge THANK YOU @sfonteneau
Re: [SOLVED] HTTP/1.1 504 Gateway Time-out
Published: February 28, 2019 - 4:11 PM
by Alesk
Hello, this works for me too, but the path used is
c:\wapt\waptpython.exe c:\wapt\waptserver\waptserver_winsetup.py -ldebug install_waptserver -cc:\wapt\conf\waptserver.ini
instead of
c:\wapt\waptpython.exe c:\wapt\waptserver\winsetup.py -ldebug install_waptserver -cc:\wapt\conf\waptserver.ini.
I don't see any c:\wapt\waptserver\winsetup.py.
Is this normal?
Thank you.
Re: [SOLVED] HTTP/1.1 504 Gateway Time-out
Published: February 28, 2019 - 4:20 PM
by Alesk
Actually, no, this is causing confusion between versions 1.5 and 1.7.
The console is telling me there's an inconsistency between the console and server versions.
When I access the URL through a browser, the interface shows version 1.5, while the server console shows version 1.7.
It doesn't make sense.
I'm restoring a snapshot while I wait for your advice on how to revert to version 1.5.
Thank you in advance for your help.