Any tips for running v3 installer on a Debian box with Nginx already running on it?

Support
1

Problem: Installer complains at the Apache stage since Nginx is running and bound on 443

Other relevant data:
uname and installer log attachedProcessing: log.log…
new users can’t upload attachments :frowning:

ok, shoving it here:

x@y:/tmp$ uname -a
Linux y 4.19.0-17-amd64 #1 SMP Debian 4.19.194-3 (2021-07-18) x86_64 GNU/Linux
x@y:/tmp$ sudo foreman-installer
2021-09-18 10:19:04 [NOTICE] [root] Loading installer configuration. This will take some time.
2021-09-18 10:19:07 [NOTICE] [root] Running installer with log based terminal output at level NOTICE.
2021-09-18 10:19:07 [NOTICE] [root] Use -l to set the terminal output log level to ERROR, WARN, NOTICE, INFO, or DEBUG. See --full-help for definitions.
2021-09-18 10:19:08 [NOTICE] [configure] Starting system configuration.
2021-09-18 10:19:13 [NOTICE] [configure] 250 configuration steps out of 1331 steps complete.
2021-09-18 10:19:14 [NOTICE] [configure] 500 configuration steps out of 1333 steps complete.
2021-09-18 10:19:14 [NOTICE] [configure] 750 configuration steps out of 1440 steps complete.
2021-09-18 10:19:14 [NOTICE] [configure] 1000 configuration steps out of 1441 steps complete.
2021-09-18 10:19:23 [ERROR ] [configure] Systemd start for apache2 failed!
2021-09-18 10:19:23 [ERROR ] [configure] journalctl log for apache2:
2021-09-18 10:19:23 [ERROR ] [configure] -- Logs begin at Sat 2021-09-18 09:48:24 PDT, end at Sat 2021-09-18 10:19:23 PDT. --
2021-09-18 10:19:23 [ERROR ] [configure] Sep 18 10:19:23 y systemd[1]: Starting The Apache HTTP Server...
2021-09-18 10:19:23 [ERROR ] [configure] Sep 18 10:19:23 y apachectl[12762]: (98)Address already in use: AH00072: make_sock: could not bind to address [::]:443
2021-09-18 10:19:23 [ERROR ] [configure] Sep 18 10:19:23 y apachectl[12762]: (98)Address already in use: AH00072: make_sock: could not bind to address 0.0.0.0:443
2021-09-18 10:19:23 [ERROR ] [configure] Sep 18 10:19:23 y apachectl[12762]: no listening sockets available, shutting down
2021-09-18 10:19:23 [ERROR ] [configure] Sep 18 10:19:23 y apachectl[12762]: AH00015: Unable to open logs
2021-09-18 10:19:23 [ERROR ] [configure] Sep 18 10:19:23 y apachectl[12762]: Action 'start' failed.
2021-09-18 10:19:23 [ERROR ] [configure] Sep 18 10:19:23 y apachectl[12762]: The Apache error log may have more information.
2021-09-18 10:19:23 [ERROR ] [configure] Sep 18 10:19:23 y systemd[1]: apache2.service: Control process exited, code=exited, status=1/FAILURE
2021-09-18 10:19:23 [ERROR ] [configure] Sep 18 10:19:23 y systemd[1]: apache2.service: Failed with result 'exit-code'.
2021-09-18 10:19:23 [ERROR ] [configure] Sep 18 10:19:23 y systemd[1]: Failed to start The Apache HTTP Server.
2021-09-18 10:19:23 [ERROR ] [configure] /Stage[main]/Apache::Service/Service[httpd]/ensure: change from 'stopped' to 'running' failed: Systemd start for apache2 failed!
2021-09-18 10:19:23 [ERROR ] [configure] journalctl log for apache2:
2021-09-18 10:19:23 [ERROR ] [configure] -- Logs begin at Sat 2021-09-18 09:48:24 PDT, end at Sat 2021-09-18 10:19:23 PDT. --
2021-09-18 10:19:23 [ERROR ] [configure] Sep 18 10:19:23 y systemd[1]: Starting The Apache HTTP Server...
2021-09-18 10:19:23 [ERROR ] [configure] Sep 18 10:19:23 y apachectl[12762]: (98)Address already in use: AH00072: make_sock: could not bind to address [::]:443
2021-09-18 10:19:23 [ERROR ] [configure] Sep 18 10:19:23 y apachectl[12762]: (98)Address already in use: AH00072: make_sock: could not bind to address 0.0.0.0:443
2021-09-18 10:19:23 [ERROR ] [configure] Sep 18 10:19:23 y apachectl[12762]: no listening sockets available, shutting down
2021-09-18 10:19:23 [ERROR ] [configure] Sep 18 10:19:23 y apachectl[12762]: AH00015: Unable to open logs
2021-09-18 10:19:23 [ERROR ] [configure] Sep 18 10:19:23 y apachectl[12762]: Action 'start' failed.
2021-09-18 10:19:23 [ERROR ] [configure] Sep 18 10:19:23 y apachectl[12762]: The Apache error log may have more information.
2021-09-18 10:19:23 [ERROR ] [configure] Sep 18 10:19:23 y systemd[1]: apache2.service: Control process exited, code=exited, status=1/FAILURE
2021-09-18 10:19:23 [ERROR ] [configure] Sep 18 10:19:23 y systemd[1]: apache2.service: Failed with result 'exit-code'.
2021-09-18 10:19:23 [ERROR ] [configure] Sep 18 10:19:23 y systemd[1]: Failed to start The Apache HTTP Server.
2021-09-18 10:19:23 [NOTICE] [configure] 1250 configuration steps out of 1441 steps complete.
2021-09-18 10:19:24 [NOTICE] [configure] System configuration has finished.

  There were errors detected during install.
  Please address the errors and re-run the installer to ensure the system is properly configured.
  Failing to do so is likely to result in broken functionality.

  The full log is at /var/log/foreman-installer/foreman.log
x@y:/tmp$
2

Is something already listening on port 443?

3

It is generally discouraged to install Foreman alongside other services on the same server (afaik the install docs also mention this). Is there any reason you have nginx already set up and running on that server? If it is a server already used for other services, I would recommend you get a second system to serve only Foreman.
If getting another system is not possible or you need to have nginx running on that system due to company regulations or similar things, you could try running foreman on another port. foreman-installer has the option --foreman-server-ssl-port that defaults to 443. If you really need that kind of setup, give foreman-installer --full-help a close read for options you might need to change. Be prepared though that this might leed to you needing to do further tweaking of your setup, especially of you are going for a more complex setup.

1 Like
4

You da man, thank you! Winning combo was:

sudo foreman-installer --foreman-server-port 84 --foreman-server-ssl-port 4434 --foreman-foreman-url "https://$(hostname -f):4434"