Hey Lennart,
On 23.05.25 10:08, Lennart.Volz--- via PacketFence-users wrote:
But on my thirst server (pf1) I cannot access the web interface.
Did you check whether a service is listening to the correct tcp port and
which service is listening there? Did you try to connect to the tcp port
using telnet or netcat to check whether a tcp connection could be made?
One thing I stumbled over is that docker-proxy didn't work after
restarting and re-configuring a container (do not remember if it has
been pf specific). I do not remember whether I found the root cause, but
it is hard to find if you do not look for it: make sure on the nic (e.g.
tcpdump) that a tcp connection is correctly initiated.
Inside the container check the same way if the tcp connection is initiated.
If this all works, the container might be broken: "Could not reliably
determine the server's fully qualified domain name" could indicate that
in a virtual server apache can't relate the incoming request to the
correct virtual server.
I'm writing this from memory and if your problem is inside the container
I could send you some more information on tuesday after looking at my
demo setup ;-).
Chris
--
Packetfence Matrix Room
https://matrix.to/#/%23packetfence:matrix.org
_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users
