Jump to content

Help: My Docker container cannot access the mapped port anymore


Recommended Posts

My server has been running for a long time and has always been running normally, but recently, all of my Dockers with a network type of bridge cannot be accessed through the ports mapped to the host computer

 

For example, I have the following containers

1373715548__20240221140908.thumb.png.70e260b5de7fa62cbb3d907fe0ac2a29.png

Nginx Proxy Manager cannot be accessed successfully through 192.168.50.95:80, and the container cannot ping the host 192.168.50.95 internally

 

My network and Docker related configurations are as follows

2043753089__20240221141206.thumb.png.3d62ba02acae2079cff502f8c0344c37.png

238516271__20240221141220.thumb.png.21bb21a6fb19d3d93599d54f98e78126.png

 

I haven't made any modifications, I just wake up and it won't work

 

Edited by medivh
Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...