Trying to access another forum but getting Access Forbidden

[lsemmens]

I have been there every day since a long time ago but now all I get is a 403 Forbidden message. I've tried a different computer, different browser, re-set my modem (dynamic IP) all to no avail. Can someone else try this address and see if they can get there.

Thanks

[RedXT]

all good here mate, windows 10 firefox 132.0

[lsemmens]

Thanks mate gonna have to muck around some more here.

[hoe]

they are blocking known vpn ip addresses

[lsemmens]

I do not use a VPN and have even tried tethering my mobile phone and using its internet. I also have the same issue on every computer in the house! What's my IP blacklist reports my address as OK. Not sure what else I can try.

[hoe]

Are you using an adblocker/private dns?

Maybe try cloud flare? 1.1.1.1

Sent from my motorola razr 50 ultra using Tapatalk

[lsemmens]

I tethered my Mobile Phone internet to the computer and forgot to disable wifi on it first so it went though my current ISP. Once I realised and fixed that problem, I could connect via the Helstra network. My home internet is with Origin and that does not work. I performed a traceroute on the site, but cannot determine who is causing it to fall over.

eigh@leigh-Satellite-P70-A:~$ traceroute salems.co.uk
traceroute to salems.co.uk (185.224.198.51), 64 hops max
1 192.168.20.1 3.263ms 2.113ms 1.813ms
2 100.108.0.1 39.355ms 41.538ms 39.451ms
3 123.176.117.81 38.118ms 30.342ms 29.812ms
4 202.90.207.120 30.877ms 41.433ms 40.129ms
5 103.200.13.175 203.535ms 207.302ms 210.584ms
6 103.200.15.69 212.213ms 209.760ms 199.051ms
7 103.200.13.67 201.482ms 211.389ms 217.998ms
8 103.200.15.66 206.976ms 210.192ms 209.480ms
9 * 103.200.13.168 216.884ms *
10 64.124.204.201 217.004ms 235.539ms 204.442ms
11 * * 64.125.28.234 352.434ms
12 64.125.28.233 347.072ms 354.449ms 354.090ms
13 64.125.26.182 356.595ms 348.512ms 349.742ms
14 * 64.125.22.77 346.805ms *
15 * * *
16 * * *
17 * * *
18 * * *
19 64.125.20.27 357.276ms 349.765ms 348.775ms
20 64.125.25.107 345.671ms 338.709ms 350.559ms
21 94.31.50.206 352.815ms 339.548ms 339.200ms
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
31 * * *
32 * * *
33 * * *
34 * * *
35 * * *
36 * * *
37 * * *
38 * * *
39 * * *
40 * * *
41 * * *
42 * * *
43 * * *
44 * * *
45 * * *
46 * * *
47 * * *
48 * * *
49 * * *
50 * * *
51 * * *
52 * * *
53 * * *
54 * * *
55 * * *
56 * * *
57 * * *
58 * * *
59 * * *
60 * * *
61 * * *
62 * * *
63 * * *
64 * * *
leigh@leigh-Satellite-P70-A:~$

[wotnot]

superloop.com satellite router has fallen over ... it's a completely different route from here....

[RedXT]

Im with exetel and site still working for me today

[lsemmens]

I left my modem off overnight and all is back to normal today, my public IP has changed from 119.xxx.xxx.xxx to 122.xxx.xxx.xxx. SO there must be some spammer somewhere using the 119 code...

[wotnot]

Nope....I doubt you're on fixed IP....

[wotnot]

Im with exetel and site still working for me today

...yeah, they use a number of backbones, you would've had to be on the same segment as OP to catch it =)

[lsemmens]

Nope....I doubt you're on fixed IP....

I'm not! I'd have considered, though, though that my provider would have used a fixed range though to prevent duplication on the www.

[wotnot]

...m'kay.... I've got nothing better to do for a few minutes.... *your* traceroute .... //annotated


traceroute to salems.co.uk (185.224.198.51), 64 hops max //DNS resolution is correct

1 192.168.20.1 3.263ms 2.113ms 1.813ms //your modem
2 100.108.0.1 39.355ms 41.538ms 39.451ms //other end...
3 123.176.117.81 38.118ms 30.342ms 29.812ms //big sucker router pooling 123.176.112.0 - 123.176.119.255
4 202.90.207.120 30.877ms 41.433ms 40.129ms //big sucker switch pooling 202.90.206.0 - 202.90.207.255
5 103.200.13.175 203.535ms 207.302ms 210.584ms //the little bugga the big suckers tossed the packets to... pools 103.200.12.0 - 103.200.15.0
6 103.200.15.69 212.213ms 209.760ms 199.051ms // f'tang
7 103.200.13.67 201.482ms 211.389ms 217.998ms // f'tang
8 103.200.15.66 206.976ms 210.192ms 209.480ms //ole!...
9 * 103.200.13.168 216.884ms * //biscuit barrel...this machine's on drugs, looks like a bridge...it's not convinced the routing info jives with it's walkman ...this is the last HOP on excetel/superloop's network...
10 64.124.204.201 217.004ms 235.539ms 204.442ms //..and now we're on a Zayo Bandwidth network segment in the US...
11 * * 64.125.28.234 352.434ms //now we're heading off into 'packet pingpong', as it's passed from one machine...
12 64.125.28.233 347.072ms 354.449ms 354.090ms //to another....
13 64.125.26.182 356.595ms 348.512ms 349.742ms //to another....
14 * 64.125.22.77 346.805ms * //to another....which denies responsibilities...
15 * * * //wtf, I beg your pardon
16 * * * //wtf, I beg your pardon
17 * * * //wtf, I beg your pardon
18 * * * //wtf, I beg your pardon
19 64.125.20.27 357.276ms 349.765ms 348.775ms //to another....
20 64.125.25.107 345.671ms 338.709ms 350.559ms //to another....
21 94.31.50.206 352.815ms 339.548ms 339.200ms //to another....
22 * * *
23 * * *
24 * * *
....and probably packet death occurred thereafter...

...to get an idea of 'what went wrong'...you'd redo the traceroute (with the same level of scrutiny), now that it's all working again, and most times you can discern "who dunnit" =)

NjOy!

[lsemmens]

Thanks wotnot, I just did another traceroute and it is almost identical the only difference is 11 * * 64.125.28.234 whereas before it ended in .233. IT works now, so It may not be worth chasing. How did you determine what each address is? That interests me.

[wotnot]

Thanks wotnot, I just did another traceroute and it is almost identical the only difference is 11 * * 64.125.28.234 whereas before it ended in .233. IT works now, so It may not be worth chasing. How did you determine what each address is? That interests me.

...once upon a time, you could pick them by name .... but regardless, the whois database registers machines, not just domain/FQDN addresses....ie; whois 64.125.28.233 .... once you get there, you check the NetHandle: value to determine roughly where abouts you are in the topology. That gets easier to look at, by using mtr instead of traceroute...

mtr -rwzc 5 185.224.198.51
Start: 2024-11-02T21:58:57+1000
HOST: gallah Loss% Snt Last Avg Best Wrst StDev
1. AS??? 192.168.1.1 0.0% 5 3.7 4.4 3.7 5.8 0.9
2. AS??? /magic_word/ 0.0% 5 36.0 37.5 35.6 40.6 2.2
3. AS7545 60-240-241-193.static.tpgi.com.au 0.0% 5 34.6 36.4 34.2 39.2 2.4
4. AS7545 203-219-107-125.static.tpgi.com.au 0.0% 5 46.5 48.0 46.5 51.0 2.1
5. AS9942 syd-gls-har-int3-be-200.tpg.com.au 0.0% 5 47.4 44.1 36.2 50.1 5.7
6. AS??? ??? 100.0 5 0.0 0.0 0.0 0.0 0.0 //transparent bridge across the Pacific
7. AS174 be3670.ccr22.sfo01.atlas.cogentco.com 0.0% 5 194.7 194.8 192.5 197.2 1.8
8. AS174 be3110.ccr32.slc01.atlas.cogentco.com 0.0% 5 205.0 207.5 205.0 211.4 2.8
9. AS174 be5456.ccr22.den01.atlas.cogentco.com 0.0% 5 214.8 215.0 205.5 219.7 5.8
10. AS174 be4995.ccr32.oma02.atlas.cogentco.com 0.0% 5 226.6 228.0 225.6 231.9 2.8
11. AS174 be5068.ccr42.ord01.atlas.cogentco.com 0.0% 5 223.4 226.4 222.1 232.7 4.1
12. AS174 be2718.ccr22.cle04.atlas.cogentco.com 0.0% 5 240.5 241.7 239.6 244.6 2.3
13. AS174 be2994.ccr32.yyz02.atlas.cogentco.com 0.0% 5 245.8 252.5 245.4 262.7 7.8
14. AS174 be3260.ccr22.ymq01.atlas.cogentco.com 0.0% 5 252.7 254.7 252.6 257.4 2.2
15. AS174 be3043.ccr22.lpl01.atlas.cogentco.com 0.0% 5 322.6 326.3 321.8 332.5 4.3
16. AS174 be2655.rcr21.dub01.atlas.cogentco.com 0.0% 5 329.1 332.0 327.7 337.9 4.0
17. AS174 be3842.nr61.b022738-0.dub01.atlas.cogentco.com 0.0% 5 323.7 329.7 323.7 340.4 6.8
18. AS174 be2512.nr61.b054533-0.dub01.atlas.cogentco.com 20.0% 5 340.0 339.1 335.6 340.7 2.4
19. AS174 149.6.5.90 0.0% 5 331.5 335.3 329.4 347.3 7.0
20. AS21130 cpanel51.fastsecurehost.com 20.0% 5 346.3 340.5 328.4 346.3 8.2

[lsemmens]

Thank you, more learning in my future methinks!