Port 443 is already in use by another process error Amazon AWS instance

I’m slightly confused by the reverse DNS discussion - I don’t see how it’s relevant to the issue - and it’s not related to the “Could not reliably determine the server’s fully qualified domain name, using 127.0.0.1. Set the ‘ServerName’ directive globally to suppress this message” message ( which is just apache config - and only a warning, it’s not stopping anything working).

2 Likes

@serverco Me neither to be honest, have no idea about AWS or Bitnami trying anything to help Eddie here

The thread is a bit long … so I’m not 100% certain on the current state of things.

Bitnami doesn’t use the standard apache locations, so certbot won’t find / read those correctly ( ie, you can’t use the auto plugin for apache).

You can use use the standalone method ( after ensuring that binami / apache is stopped) or you can use the webroot method. - https://certbot.eff.org/docs/using.html#webroot

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.