No idea where to find my error

Help
21

I did what ou suggested last time. I forwarded to a different virtual server with a fresh apache server on port 80.
it was working with broehlis url.

so the NAT is ok and was working for years …
I checked status of ubuntu firewall and status gave me disabled …

22

Just to confirm, you’re using iptables to check this and not ufw, right?

Could be some Docker networking shenanigans, although I’ve never seen it before. If the issue is definitely on the Caddy host’s end, it would imply that there IS some packet filtering going on, and that it’s excluding packets from non-private networks for some reason.

23

I did indeed just checked ufw

Chain INPUT (policy ACCEPT)
target     prot opt source               destination

Chain FORWARD (policy DROP)
target     prot opt source               destination
DOCKER-ISOLATION  all  --  anywhere             anywhere
ACCEPT     all  --  anywhere             anywhere             ctstate RELATED,ESTABLISHED
DOCKER     all  --  anywhere             anywhere
ACCEPT     all  --  anywhere             anywhere
ACCEPT     all  --  anywhere             anywhere
ACCEPT     all  --  anywhere             anywhere             ctstate RELATED,ESTABLISHED
DOCKER     all  --  anywhere             anywhere
ACCEPT     all  --  anywhere             anywhere
ACCEPT     all  --  anywhere             anywhere

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination

Chain DOCKER (2 references)
target     prot opt source               destination
ACCEPT     tcp  --  anywhere             172.17.0.10          tcp dpt:http
ACCEPT     tcp  --  anywhere             172.17.0.10          tcp dpt:https
ACCEPT     tcp  --  anywhere             172.17.0.12          tcp dpt:mysql
ACCEPT     tcp  --  anywhere             172.17.0.11          tcp dpt:mysql
ACCEPT     tcp  --  anywhere             172.17.0.9           tcp dpt:9001
ACCEPT     tcp  --  anywhere             172.17.0.9           tcp dpt:1883
ACCEPT     tcp  --  anywhere             172.17.0.4           tcp dpt:http
ACCEPT     tcp  --  anywhere             172.17.0.4           tcp dpt:https
ACCEPT     tcp  --  anywhere             172.17.0.8           tcp dpt:http
ACCEPT     tcp  --  anywhere             172.17.0.3           tcp dpt:mysql
ACCEPT     tcp  --  anywhere             172.17.0.5           tcp dpt:8384
ACCEPT     tcp  --  anywhere             172.17.0.7           tcp dpt:9000
ACCEPT     tcp  --  anywhere             172.17.0.13          tcp dpt:http
ACCEPT     tcp  --  anywhere             172.17.0.13          tcp dpt:https
ACCEPT     tcp  --  anywhere             172.17.0.14          tcp dpt:http-alt
ACCEPT     tcp  --  anywhere             172.17.0.6           tcp dpt:https
ACCEPT     tcp  --  anywhere             172.17.0.6           tcp dpt:http

Chain DOCKER-ISOLATION (1 references)
target     prot opt source               destination
DROP       all  --  anywhere             anywhere
DROP       all  --  anywhere             anywhere
RETURN     all  --  anywhere             anywhere
24

I am still fighting.

I stopped caddy container on my main server and added a nginx container.
This one is also accessable with port 80 from outside.
Next will be adding a fresh cady container and then I will try to access it in the same way …

25

YAHOOOOOOOO

We were maybe all a little blind …
find the mistake

############################################
pass.homer-s.my-wan.de
#bitwarden
proxy / https://192.168.100.70:443 {
transparent
websocket
insecure_skip_verify
}
log /etc/log/pass_access.log
errors /etc/log/pass_errors.log
tls mymail@mail.de
}

SO MANY THANKS TO ALL OF YOU!!!

26

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.