Traffic not making it through ip.afrihost.co.za

TrueTenacity

Senior Member
Joined
Feb 19, 2005
Messages
762
Reaction score
13
Location
Johannesburg, South Africa
My docker server went haywire and I though it's been a year and a half since I set it up, I'll re-do the whole server while trying to fix it.

I've followed the guide and everything is setup and working locally but absolutely nothing works the moment I try to access anything via my domain.

Traefik is setup and working locally, the ports are option (I've even turned off *ALL* the firewalls to see if it was that) and nothing gets through...

It worked perfectly when I set it up the same way last time, but now everything, including the traceroutes just timeout.

Tracing route to dannyb8.ip.afrihost.co.za [102.182.106.127]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms RT-AX58U.local [10.0.0.1]
2 3 ms 1 ms 1 ms 100.98.84.1
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.
 
My docker server went haywire and I though it's been a year and a half since I set it up, I'll re-do the whole server while trying to fix it.

I've followed the guide and everything is setup and working locally but absolutely nothing works the moment I try to access anything via my domain.

Traefik is setup and working locally, the ports are option (I've even turned off *ALL* the firewalls to see if it was that) and nothing gets through...

It worked perfectly when I set it up the same way last time, but now everything, including the traceroutes just timeout.

Tracing route to dannyb8.ip.afrihost.co.za [102.182.106.127]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms RT-AX58U.local [10.0.0.1]
2 3 ms 1 ms 1 ms 100.98.84.1
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

Hi

What line are you tracing from? I'm tracing to that ddns name and the destination is not responding to icmp. I see the connection you are tracing from is a natted IP connection.
 
Hi

What line are you tracing from? I'm tracing to that ddns name and the destination is not responding to icmp. I see the connection you are tracing from is a natted IP connection.
Maybe he is natted. When I tested a static ip on my Openserve line it was natted, which is the way it's been done since 2017, and lost contact with my network...

OP, you can ask for a non-natted ip... or the safer option to having open ports on your router, use a cloudflare tunnel with your domain. I access my home server using that, no need to open ports on the router.
 
When I first setup this server, I got it working by using my ip.afrihost.co.za address in the dns config on cloudflare.
I've just rebuilt the whole docker stack again and when I fired up traefik, it threw an error that makes it all clear...

"cloudflare: failed to find zone ip.afrihost.co.za.: zone could not be found"

So it's not that the traffic isn't getting through. It can't generate a certificate because of the non-standard dns config.

The only way around that is a proper public IP.
 
@IamNoone

I was using tunnels just like that actually! Might be the only way to go...
Well it works. Cloudflares tunnel is always active between the server and their system. I added 2fa with the need to enter a pre-approved email address, which if it exists, sends an otp to that email.
 
Top
Sign up to the MyBroadband newsletter
X