# Driver failed programming external connectivity on endpoint pmm-server **URL:** \ **Category:** Percona Monitoring and Management (PMM)\ **Created:** [July 5, 2023, 7:17am UTC](https://forums.percona.com/t/driver-failed-programming-external-connectivity-on-endpoint-pmm-server/23365 "2023-07-05T07:17:41Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![farhan.ext](https://avatars.discourse-cdn.com/v4/letter/f/6f9a4e/32.png) [@farhan.ext](https://forums.percona.com/u/farhan.ext)\ **Post date:** [July 5, 2023, 7:17am UTC](https://forums.percona.com/t/driver-failed-programming-external-connectivity-on-endpoint-pmm-server/23365/1 "2023-07-05T07:17:41Z")
Hello, I am getting below error while starting the container for PMM, please help. earlier it was running fine and I change the docker volumes path from /var/lib/docker to other mountpoint due to storage consumption and after that its not getting started. [root@sqlrtr05 var]# docker start pmm-server Error response from daemon: driver failed programming external connectivity on endpoint pmm-server (8f185c26af9fd35791c198ee4fa82378f719dff3e66a06c5fcaef9bc48ddcd8d): Bind for 0.0.0.0:443 failed: port is already allocated Error: failed to start containers: pmm-server [root@sqlrtr05 var]# docker ps -a CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 051e3e9cf0a6 percona/pmm-server:2.37.0 “/opt/entrypoint.sh” 44 hours ago Created pmm-server 83c7c4e89fb9 percona/pmm-server:2.37.0 “/bin/true” 6 weeks ago Created pmm-data [root@sqlrtr05 var]# ---
**Author:** ![Michael\_Coburn](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/michael_coburn/32/18_2.png) [@Michael\_Coburn](https://forums.percona.com/u/Michael_Coburn)\ **Post date:** [July 5, 2023, 3:02pm UTC](https://forums.percona.com/t/driver-failed-programming-external-connectivity-on-endpoint-pmm-server/23365/2 "2023-07-05T15:02:37Z")
Hi @farhan.ext thank you for posting to the Percona forums! This error is being reported because something is already running on port `443/tcp` which is probably the `pmm-server` container. You can try by doing a `docker stop pmm-server` container, rename it `docker rename pmm-server pmm-server-backup`, then do a `docker run`, let us know how that goes! ---
**Author:** ![farhan.ext](https://avatars.discourse-cdn.com/v4/letter/f/6f9a4e/32.png) [@farhan.ext](https://forums.percona.com/u/farhan.ext)\ **Post date:** [July 6, 2023, 7:39am UTC](https://forums.percona.com/t/driver-failed-programming-external-connectivity-on-endpoint-pmm-server/23365/3 "2023-07-06T07:39:55Z")
> [@Michael\_Coburn](#): > > docker rename pmm-server pmm-server-backup Hello @Michael_Coburn , I ran the below commands as suggested and logs are as below, please let me know what I am doing wrong and how we can fix this: [root@tmpsrv ~]# docker ps -a CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 051e3e9cf0a6 percona/pmm-server:2.37.0 “/opt/entrypoint.sh” 2 days ago Created pmm-server 83c7c4e89fb9 percona/pmm-server:2.37.0 “/bin/true” 6 weeks ago Created pmm-data [root@tmpsrv ~]# docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES [root@tmpsrv ~]# docker stop pmm-server pmm-server [root@tmpsrv ~]# docker rename pmm-server pmm-server-backup [root@tmpsrv ~]# [root@tmpsrv ~]# docker run --detach --restart always \ > –publish 443:443 > -v pmm-data:/apps/docker > –name pmm-server > percona/pmm-server:2.37.0 > fd7adc50a22f3a0f9a3c9b1d5b5a7d01249c77a87c94c53a1da52830029fa936 > /usr/bin/docker-current: Error response from daemon: driver failed programming external connectivity on endpoint pmm-server (2ae5f366a4fb58764b5d02bc657e4bd3baf725045b414213829d756bcdc36ca6): Bind for 0.0.0.0:443 failed: port is already allocated. [root@tmpsrv ~]# docker ps -a CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES fd7adc50a22f percona/pmm-server:2.37.0 “/opt/entrypoint.sh” 55 seconds ago Created pmm-server 051e3e9cf0a6 percona/pmm-server:2.37.0 “/opt/entrypoint.sh” 2 days ago Created pmm-server-backup 83c7c4e89fb9 percona/pmm-server:2.37.0 “/bin/true” 6 weeks ago Created pmm-data [root@tmpsrv ~]# [root@tmpsrv ~]# docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES [root@tmpsrv ~]# ---
**Author:** ![farhan.ext](https://avatars.discourse-cdn.com/v4/letter/f/6f9a4e/32.png) [@farhan.ext](https://forums.percona.com/u/farhan.ext)\ **Post date:** [July 10, 2023, 9:11am UTC](https://forums.percona.com/t/driver-failed-programming-external-connectivity-on-endpoint-pmm-server/23365/4 "2023-07-10T09:11:37Z")
Hello @Michael_Coburn, can you please advise what I am missing here? ---
**Author:** ![Michael\_Coburn](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/michael_coburn/32/18_2.png) [@Michael\_Coburn](https://forums.percona.com/u/Michael_Coburn)\ **Post date:** [July 10, 2023, 1:35pm UTC](https://forums.percona.com/t/driver-failed-programming-external-connectivity-on-endpoint-pmm-server/23365/5 "2023-07-10T13:35:11Z")
> [@farhan.ext](#): > > Bind for 0.0.0.0:443 failed: port is already allocated. You have something listening on port 443 already. Can you please execute: ```auto docker stop pmm-server docker ps -a | grep 443 ``` This will tell us if there is another container using port `443/tcp` ---
**Author:** ![farhan.ext](https://avatars.discourse-cdn.com/v4/letter/f/6f9a4e/32.png) [@farhan.ext](https://forums.percona.com/u/farhan.ext)\ **Post date:** [July 11, 2023, 5:41am UTC](https://forums.percona.com/t/driver-failed-programming-external-connectivity-on-endpoint-pmm-server/23365/6 "2023-07-11T05:41:51Z")
Dear @Michael_Coburn, please find below the status of your commands, there is nothing on 443 port but this error is not going away. Should I load the pmm image again and create another volumn? [root@tmpsrv ~]#docker stop pmm-server pmm-server [root@tmpsrv ~]#docker ps -a | grep 443 [root@tmpsrv ~]# ---
**Author:** ![Michael\_Coburn](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/michael_coburn/32/18_2.png) [@Michael\_Coburn](https://forums.percona.com/u/Michael_Coburn)\ **Post date:** [July 11, 2023, 1:58pm UTC](https://forums.percona.com/t/driver-failed-programming-external-connectivity-on-endpoint-pmm-server/23365/7 "2023-07-11T13:58:43Z")
Then it seems like you have something else listening on `443/tcp` , can you check: ```auto ss -4np | 443 ``` This will display network sockets for IPV4 in numerical format and to share the name of the listening process. ---
**Author:** ![farhan.ext](https://avatars.discourse-cdn.com/v4/letter/f/6f9a4e/32.png) [@farhan.ext](https://forums.percona.com/u/farhan.ext)\ **Post date:** [July 18, 2023, 4:30pm UTC](https://forums.percona.com/t/driver-failed-programming-external-connectivity-on-endpoint-pmm-server/23365/8 "2023-07-18T16:30:08Z")
Dear @Michael_Coburn , ss -4np | grep 443 is showing nothing