# Unable to access ssl/443 port/ listen tcp4 127.0.0.1:443: bind: address already in use

**URL:** <https://forum.greenbone.net/t/unable-to-access-ssl-443-port-listen-tcp4-127-0-0-1-bind-address-already-in-use/19506>\
**Category:** Community Containers\
**Created:** [October 28, 2024, 9:10am UTC](https://forum.greenbone.net/t/unable-to-access-ssl-443-port-listen-tcp4-127-0-0-1-bind-address-already-in-use/19506 "2024-10-28T09:10:34Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![yoo](https://forum.greenbone.net/letter_avatar/yoo/32/6_449c533f586939b6e5f246632a46421f.png) [@yoo](https://forum.greenbone.net/u/yoo)\
**Post date:** [October 28, 2024, 9:10am UTC](https://forum.greenbone.net/t/unable-to-access-ssl-443-port-listen-tcp4-127-0-0-1-bind-address-already-in-use/19506/1 "2024-10-28T09:10:34Z")

</div>

Unable to access ssl/443 port/ bind: address already in use

intent to setup ssl to the docker container using the docker-compose.yml file failed with the following Error:

Error response from daemon: driver failed programming external connectivity on endpoint greenbone-community-edition-gsa-1 (09d6658ad2ff85e23f68dbdf09ea9e7f90eeca008eea66ec0480c3543ad2c10f): Error starting userland proxy: listen tcp4 127.0.0.1:443: bind: address already in use

no service is listening on port 443. i have check that with sudo lsof -i -P -n and with grep 443 and sudo ss -tulpn | grep 443:

The docker-compose.yml gsa section:  
If i remove - 127.0.0.1:443:443 no error appears but no service is listening on 443. The docker container still unusable.

gsa:  
image: [registry.community.greenbone.net/community/gsa:stable](http://registry.community.greenbone.net/community/gsa:stable)  
restart: on-failure  
environment:  
- GSAD\_ARGS=–no-redirect --http-sts --gnutls-priorities=SECURE256:-VERS-TLS-ALL:+VERS-TLS1.2:+VERS-TLS1.3  
ports:  
- 127.0.0.1:9293:80  
# Make GSA accessible locally on port 443  
- 127.0.0.1:443:443  
# Make GSA accessible remotely on port 443  
- 443:443  
volumes:  
# Move the private key into the container. Replace with your own.  
- /home/test-user/.ssl/serverkey.pem:/var/lib/gvm/private/CA/serverkey.pem  
# Move the certificate into the container Replace with your own.  
- /home/test-user/.ssl/servercert.pem:/var/lib/gvm/CA/servercert.pem  
- gvmd\_socket\_vol:/run/gvmd

How can I solve this ( listen tcp4 127.0.0.1:443: bind: address already in use) problem?  
Many Thanks!

---

<div class="post-metadata">

**Author:** ![yoo](https://forum.greenbone.net/letter_avatar/yoo/32/6_449c533f586939b6e5f246632a46421f.png) [@yoo](https://forum.greenbone.net/u/yoo)\
**Post date:** [November 4, 2024, 12:24pm UTC](https://forum.greenbone.net/t/unable-to-access-ssl-443-port-listen-tcp4-127-0-0-1-bind-address-already-in-use/19506/2 "2024-11-04T12:24:10Z")

</div>

SOLVED

after testing several possible sources of error. I found that this error has to do with the permissions of the SSL certificate.

After changing the permission with chmod 640:  
-rw-r-- 1 user servercert.pem  
-rw-r-- 1 user serverkey.pem

SSL works correctly.

---

<div class="post-metadata">

**Author:** ![system](https://forum.greenbone.net/uploads/default/original/2X/4/4660e797edfaea797a8c9965246072ea26732804.png) [@system](https://forum.greenbone.net/u/system)\
**Post date:** [April 7, 2025, 10:24am UTC](https://forum.greenbone.net/t/unable-to-access-ssl-443-port-listen-tcp4-127-0-0-1-bind-address-already-in-use/19506/3 "2025-04-07T10:24:01Z")

</div>

Closed on April 7, 2025, 10:24am UTC


