[RESOLVED] nginx 504 gateway timeout when upgrading to 1.7

Questions about WAPT Server / Requests and help related to the WAPT server
Forum Rules
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
Locked
User avatar
olivetree
Messages: 28
Registration: February 19, 2018 - 10:42
Location: Orsay
Contact :
Contact olivetree

February 18, 2019 - 11:24

Good morning.

Windows Server 2012r2
Testing the upgrade from version 1.5 to 1.7

Manipulation performed
1) Backup of configuration files
2) VM backup
3) WAPT* services discontinuation
4) WAPT update from 1.5 to 1.7
5) Launch of WaptConsole
time out
A netstat from the server indicates that wapt is listening on port 443 but not on port 80
6) Launching WaptConsolePostConf
I have a result, whereas in version 1.5 it was functional.
wapt.PNG
wapt.PNG (22.68 KB) Viewed 8452 times
Last edited by olivetree on 18 Feb 2019 - 16:32, edited 2 times.
--
/r/ComedyCemetery/ "If I install Windows 10 of 32 bits twice... Will it become 64 bits?"
System Management Blog https://deployadmin.com/
High
User avatar
olivetree
Messages: 28
Registration: February 19, 2018 - 10:42
Location: Orsay
Contact :
Contact olivetree

February 18, 2019 - 1:14 PM

I don't know how to mark this as "Resolved".

The problem was between the chair and the keyboard.
The shutdown of services related to WAPT Server, particularly nginx, wasn't done properly.

Sorry for the inconvenience.
--
/r/ComedyCemetery/ "If I install Windows 10 of 32 bits twice... Will it become 64 bits?"
System Management Blog https://deployadmin.com/
High
Elminio
Messages: 33
Registration: February 19, 2016 - 3:39 PM

February 18, 2019 - 2:10 PM

Hello,
You need to edit your message and add [RESOLVED] to the title.
Can you confirm that your WAPT server is communicating correctly with your client machines?
I also need to perform this update.
Regards,
Elminio
High
User avatar
olivetree
Messages: 28
Registration: February 19, 2018 - 10:42
Location: Orsay
Contact :
Contact olivetree

February 18, 2019 - 4:31 PM

Good morning.

Yes, my server communicates with clients.
I just had to ensure the (clean) shutdown of services related to WAPT and of course proceed with the update as a local admin.
wapt2.PNG
wapt2.PNG (119.56 KB) Viewed 8440 times
--
/r/ComedyCemetery/ "If I install Windows 10 of 32 bits twice... Will it become 64 bits?"
System Management Blog https://deployadmin.com/
High
Locked

Return to "WAPT Server"


  • To go further with WAPT