Tranquil IT Forum

Good evening,
I just installed WAPT server on a Windows server 2012 and didn't have too many problems with the configuration.
However, when I add a package from an internet search or from a file downloaded from the website and loaded locally via the console, I get an error message: "

An unhandled exception has occurred.
HTTPError: 400 Client Error: Bad request for url:
....:444/upload_package/pkg-adobereader_11.9-3_x86.w..."

I should mention that in my default installation, I had to:
1) disable an Apache service present on the server;
2) after installing WAPT, I modified the WAPT Apache configuration (httpd.conf): I replaced ports 80 and 443 with 8081 and 444 in two places in this file: Listen and Virtual Host;
3) restart WAPT Apache and test from a client PC on both ports (OK
); 4) restart my other Apache server, which was listening on 80 and 443, and it also worked fine.

I've already received a message I encountered a similar error when trying to generate a WAPT agent, but ultimately the file creation was successful, and my client had the correct (and up-to-date) server credentials with the correct ports.

However, I also don't see my client on the console (this might be related to my client PC firewall being active, but that's a minor issue for now).

If anyone has any ideas about the error message preventing me from adding applications, I'd appreciate it.

Okay, so I ran some more tests:
- On my 2012 server, I found 2-3 configuration files still using ports 80 and 443 in c:\wapt
=> modifying them and restarting Apache didn't change anything.
- On a Windows 7 machine, I installed Wapt Server without changing any ports, and I get the same error when uploading a package.
- The same thing happens when disabling the firewall on the Windows 7 PC.

I'm going to test the Windows 7 PC again with a direct internet connection to eliminate any doubt about the site's internal firewall.
Since I tested using a .wapt file previously downloaded to my Windows 7 machine, I shouldn't need a network connection to add my package anymore, right?

With direct internet access, it works (I installed and configured everything from start to finish using my mobile internet connection).
I've noticed that the server is recognized in the inventory tab of the console, which isn't even the case on my Windows 7 machine or my server.

So, is the WAPT console constantly communicating over the internet?
That's the only explanation I can see for why local server detection only works on my machine, which is connected via mobile internet.

What should I test or check in my firewall settings to resolve this?

An internet connection is only required for package import if the external repository is on the internet.
In this case, if the site uses a proxy, it must be enabled in the console to access the external repository (no automatic detection).

However, the custom port 444 for HTTPS might not be handled correctly in the console... we haven't tested with a port other than 443.

Do you have an active antivirus program that intercepts and scans HTTP/HTTPS requests?