Join Log in
Score:0
Ryuunosuke avatar Ubuntu

Container can't connect to host public ip after ip change

ng flag
Ryuunosuke

First of all hello y'all.

I've been working on a docker server for my company with several containers. One of them is an apache container with proxy enabled in order to proxy reverse the adress of the other containers removing the port. For example myip:3000 would be grana.my.domain. the redirection is working properly on the dns server.

When i was setting up the server, i had an specific ip in order to access the internet, but my ip changed. And with that change my apache proxy stoped working.

It is set up like this:

<VirtualHost *:80>
        ProxyPass / http://publicip:3000/
        ProxyPassReverse / http://publicip:3000/
        ServerName grafana.my.domain
    </VirtualHost>

Apache is not the only one unable to access the public ip of the host machine. None of the working containers can do it. Am i doing something wrong? What am i missing? It was working perfectly fine before the ip changed.

59
0 + 0
ip
ธงชาติไทย
Elon Musk
I sit in a Tesla and translated this thread with Ai:

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.