Discussion - Best way to fix listen tcp 0.0.0.0:443: bind: address already in use\")"} | PlexGuide.com

Discussion Best way to fix listen tcp 0.0.0.0:443: bind: address already in use\")"}

  • Stop using Chrome! Download the Brave Browser via >>> [Brave.com]
    It's a forked version of Chrome with native ad-blockers and Google's spyware stripped out! Download for Mac, Windows, Android, and Linux!
Welcome to the PlexGuide.com
Serving the Community since 2016!
Register Now

WR138

Citizen+
Original poster
Nov 23, 2019
15
2
I was able find a few posts on this but I didn't find anything that showed a resolution after more than a day looking.

I know what is using it, apache.

sudo netstat -ntulp | grep 443
tcp6 0 0 :::443 :::* LISTEN 6986/apache2

But if i stop apache then I get an error, can’t connect to the server or a 521 error.

To add the SSL and Origin Server stuff I couldn't find anything showing how to set it up without apache.

The question is what is the best way to resolve this and how.

Remove apache? But then what about my SSL and Origin Server certs and key?

Move a port assignment and for what application, (least impacting).

I'm sure the answer is obvious to somone tht will read this. Even a link to the exact wiki that addresses this would be super helpful and I am willing to start from scratch if need be. If any information is missing that might help please ask because there is a chance I may be even looking at the wrong spot.
1579385223305.png
Thanks.

This is what I have set up
Domain is Google with Cloudflare, Ubuntu 18.4 on a Hetzner deti
Hetzner

DNS

1579385223305.png

No wildcard.
Post automatically merged:

passing this on, it fixed it for me.

sudo nano /etc/apache2/ports.conf
Then change the Listen line from 80 to 8082

sudo nano /etc/apache2/sites-available/000-default.conf
Then change the VirtualHost directive in the file header from 80 to 8082

sudo nano /etc/apache2/sites-available/default-ssl.conf
Then change the port from 443 to 444

sudo systemctl restart apache2.service

Check

sudo netstat -ntulp | grep 443

if there is still apache use look at sudo nano /etc/apache2/ports.conf and see if there are "if" rules teid in with the SSL still going to 443 and change those to 444.
 
Last edited:

Recommend NewsGroups

      Up To a 58% Discount!