[SOLVED] tis-remote-repo-http - Installation failed

[silica]

Good morning,

I am encountering an error installing the tis-remote-repo-http package on a Windows 11 PC

The Wapt console is back:

Code: Select all

installing si-remote-repo-http(=2.6.0.17177-10)
Install wapthttpserver to permit WAPTAgent to become a repository
Remove firewall rule
Copy binary file for wapthttpserver
Install wapthttpserver
Register wapthttpserver frontend
Checking if ports 80 and 443 are available
Port 80 is not available
Traceback (most recent call last):
  File "C:\Program Files (x86)\wapt\common.py", line 4296, in install_wapt
    exitstatus = setup.install()
  File "C:\windows\TEMP\waptz7bi86u9\setup.py", line 130, in install
  File "C:\windows\TEMP\waptz7bi86u9\setup.py", line 102, in install_wapthttpserver_service
  File "C:\windows\TEMP\waptz7bi86u9\setup.py", line 78, in make_wapthttpserver_config
  File "C:\Program Files (x86)\wapt\common.py", line 3957, in run
    return ensure_unicode(run(*arg, pidlist=self.pidlist,**args))
  File "C:\Program Files (x86)\wapt\waptutils.py", line 2214, in run
    raise CalledProcessErrorOutput(proc.returncode, cmd, ''.join(output))
waptutils.CalledProcessErrorOutput: Command 'wapt-get checkport 0.0.0.0:80' returned non-zero exit status 0.
Output:0.0.0.0:80: 1


Exit code: 0



CalledProcessErrorOutput: Command 'wapt-get checkport 0.0.0.0:80' returned non-zero exit status 0.
Output:0.0.0.0:80: 1


Exit code: 0

IIS features were enabled on this PC (without any particular configuration behind it), I thought that was the reason.
I uninstalled those features but the error message is the same.

Can you help me?

Sincerely

[silica]

Indeed, by running this live on the Windows 11 PC:

Code: Select all

C:\Program Files (x86)\wapt>wapt-get checkport 0.0.0.0:80
0.0.0.0:80: 1


Exit code: 0

I get the same thing as with the package tis.
Wapt considers this result an error.

Is this an error in the package?

[dcardon]

Hello Kevin,

as mentioned in the message a little bit above:

Code: Select all

Port 80 is not available

There must already be a web server running on the machine in question

Sincerely,

Denis

[dcardon]

Hi Kevin,

were you able to fix your problem? Was something listening on port 80?

Regards,

Denis

[silica]

Good morning,

My apologies for the delayed response.

I couldn't find exactly what was listening in port 80.

I ended up replacing port 80 with 8080 in the tis-remote-repo-http
The installation was successful and the packages are synchronizing

But at the end of the synchronization, the repository fails to display an error in the console, and here are the details:

wapt.png (22.97 KB) Viewed 19853 times

Do you have any idea?

[sfonteneau]

Hello,

this happens when you disable WADs on the WAPT server and enable WADs synchronization on the secondary repository.

It tries to download the WADs files but gets a 404 error because the server returns a 404 if WADs is not enabled.

The simplest solution in your case is to enable WADs in the postconf file to see if that resolves the issue.

[dcardon]

Hello Kevin,

Regarding the port, you can run the following command which gives you the process associated with the port (OwningProcess column):

Code: Select all

Get-NetTCPConnection -State Listen | Where localport -eq '80'

Sincerely,

Denis

[silica]

Good morning,

This is a System process:

80.png (79.04 KB) Viewed 19424 times

[silica]

Hello

, this happens when the WADs functionality is disabled on the WAPT server side and WADs synchronization is enabled on the secondary repository side.

It tries to download the WADs files but gets a 404 error because the server returns a 404 if WADs is not enabled.

The simplest solution in your case is to enable WADs in the postconf to see if that resolves the issue.

Good morning,

I just restarted the postconf and I'm getting this error at the end

Code: Select all

[*] Postconfiguration completed.                                                                                                               │
│ Error while trying to configure Nginx!                                                                                                         │
│ errno = 1  output: Job for nginx.service failed because the control process exited with error code.                                            │
│ See "systemctl status nginx.service" and "journalctl -xe" for details.

Please connect to https://wapt.mon.domaine/ to access the server. 

Nginx no longer starts...

(The data is anonymized.)

Code: Select all

[root@srv tmp]# systemctl status nginx.service
● nginx.service - The nginx HTTP and reverse proxy server
   Loaded: loaded (/usr/lib/systemd/system/nginx.service; enabled; vendor preset: disabled)
  Drop-In: /etc/systemd/system/nginx.service.d
           └─nginx_worker_files_limit.conf
   Active: failed (Result: exit-code) since Tue 2025-06-24 15:31:19 CEST; 2min 55s ago
 Main PID: 1634 (code=killed, signal=KILL)

Jun 24 15:31:18 wapt.mon.domaine systemd[1]: Starting The nginx HTTP and reverse proxy server...
Jun 24 15:31:19 wapt.mon.domaine nginx[49947]: nginx: [emerg] SSL_CTX_use_PrivateKey("/opt/wapt/waptserver/ssl/key.pem") failed (S>
Jun 24 15:31:19 wapt.mon.domaine nginx[49947]: nginx: configuration file /etc/nginx/nginx.conf test failed
Jun 24 15:31:19 wapt.mon.domaine systemd[1]: nginx.service: Control process exited, code=exited status=1
Jun 24 15:31:19 wapt.mon.domaine systemd[1]: nginx.service: Failed with result 'exit-code'.
Jun 24 15:31:19 wapt.mon.domaine systemd[1]: Failed to start The nginx HTTP and reverse proxy server.

[sfonteneau]

Strange, it looks like someone has modified /opt/wapt/waptserver/ssl/key.pem; nginx can no longer open it