Hello, I recently installed Waptserver version 1.7.4.6077 on a VM (Windows Server 2008). I completed the entire installation, but when I try to authenticate, I get the following message: "Error on the WAPT server: HTTP/1.1 404 Not Found."
Any ideas on how to resolve this issue? Thank you in advance for your help.
[SOLVED] HTTP/1.1 404 Not Found
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
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
- dcardon
- WAPT Expert
- Messages: 1932
- Registration: June 18, 2014 - 09:58
- Location: Saint Sébastien sur Loire
- Contact :
Hello Glasgow,

Sincerely,
Denis
My crystal ball is broken, but my intuition tells me there's already a web server other than WAPT's running on this machine. If that's not the case, we'll need a bit more context to find an explanationGlasgow wrote: ↑June 24, 2019 - 4:56 PM Hello, I recently installed Waptserver version 1.7.4.6077 on a VM (Windows Server 2008). I completed the entire installation, but when I try to authenticate, the following message appears: "Error on the WAPT server: HTTP/1.1 404 Not Found."
Any idea how to resolve this issue? Thank you in advance for your replies.
Sincerely,
Denis
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
This morning I was able to access the console without any problems, but recently it's back to the same message as yesterday and I can't access the WAPT console
- Attachments
-
- Untitled.png (8.6 KB) Viewed 7628 times
-
- 1.png (16.75 KB) Viewed 7628 times
- sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
To verify Denis's theory:
Verify that port 8088 is listening on the machine:
The order must return:
The value 3916 represents the ID of the process that is using the port.
To verify that it is indeed the WAPT server using this port, you can list the processes and filter by the ID returned previously using the command:
The order must return:
The same applies to ports 80 and 443, but in this case, it shouldn't be waptpython.exe that responds, but nginx.exe
You can also provide us with the status of the WAPT service in services.msc
Verify that port 8088 is listening on the machine:
Code: Select all
netstat -ano | find ":8088"Code: Select all
TCP 0.0.0.0:8088 0.0.0.0:0 LISTENING 3916To verify that it is indeed the WAPT server using this port, you can list the processes and filter by the ID returned previously using the command:
Code: Select all
tasklist | find "3916"Code: Select all
waptpython.exe 3916 Services 0 34 860 KoaThe same applies to ports 80 and 443, but in this case, it shouldn't be waptpython.exe that responds, but nginx.exe
You can also provide us with the status of the WAPT service in services.msc
Thank you for your response
For port 8088, the order returns
and indeed the find me command returns
Ports 80 and 443 are responding correctly to nginx.exe
For port 8088, the order returns
Code: Select all
TCP 127.0.0.1:8088 0.0.0.0.0 LISTENING 1660Code: Select all
waptpython.exe 1660 Services 0 57 452 Ko- Attachments
-
- service.png (9.12 KB) Viewed 7621 times
- sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
Oops, my mistake, try with port 8080 and not 8088
- sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
You should carefully reread the first recommendations on this page: https://www.wapt.fr/fr/doc/waptserver-i ... index.html
