Can't reach justemail.net
 

A month or two ago (maybe longer), my browser stopped being able to reach justemail.net or www.justemail.net.

This is not a deal breaker. My browser is able to reach fastmail.fm. I am able to login by adding "@justemail.net" to my user name.

Curious, is anybody else able to reach justemail.net? Am I the only one with the problem? Did fastmail let go of the domain?

I can reach https://www.justemail.net without trouble. It should just end up redirecting you.

Have you tried running a traceroute to see where the communication with the server is breaking down? There is probably some kind of routing problem. You could try changing the DNS servers (I use Google's 8.8.8.8 and 8.8.4.4). Using a VPN might also fix the issue.

tracepath justemail.net
 

Here is what I get running tracepath on chromebook:

crosh> tracepath justemail.net
1?: [LOCALHOST] pmtu 1500
1: CR1000A.mynetworksettings.com 5.463ms
1: CR1000A.mynetworksettings.com 1.860ms
2: lo0-100.WASHDC-VFTTP-328.verizon-gni.net 5.174ms
3: ae1328-20.WASHDCDN-MSE01-AA-IE1.verizon-gni.net 24.626ms
4: no reply
5: 204.148.170.122 9.365ms
6: 172.70.132.2 6.549ms
7: 172.70.37.15 6.782ms asymm 6
8: 172.70.33.195 4.051ms asymm 7
9: 172.71.221.28 5.500ms asymm 8
10: no reply
11: no reply
12: no reply
13: no reply
14: no reply
15: no reply
16: no reply
17: no reply
18: no reply
19: no reply
20: no reply
21: no reply
22: no reply
23: no reply
24: no reply
25: no reply
26: no reply
27: no reply
28: no reply
29: no reply
30: no reply
Too many hops: pmtu 1500
Resume: pmtu 1500

Managed to reach it once just now but it was very slow to load.
Subsequent tries to reach it are now timing out.
I am in the UK.

The TRACE definitely suggests a network routing problem. If you look at the output starting at 172.70.37.15 6.782ms asymm 6, those "asymm's are very suspicious. This page has an explanation of what they mean: https://answers.launchpad.net/ubuntu...+question/7682

This is occurring before the network packets get near Fastmail's datacentre, and when I do a traceroute (or Windows TRACERT) it is clean in spite of doing this all the way from Thailand.

I'm in Scotland.

C:\>tracert www.justemail.net

Tracing route to www.justemail.net [103.168.172.65]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 22 ms 8 ms 7 ms 10.53.39.49
3 10 ms 11 ms 9 ms sgyl-core-2a-ae76-650.network.virginmedia.net [62.252.41.97]
4 * * * Request timed out.
5 15 ms 14 ms 12 ms tcma-ic-2-ae9-0.network.virginmedia.net [62.253.174.178]
6 17 ms 13 ms 15 ms 162.158.32.254
7 15 ms 18 ms 20 ms 162.158.32.11
8 15 ms 14 ms 12 ms 172.69.79.98
9 14 ms 17 ms 13 ms 172.69.79.114
10 21 ms 16 ms 18 ms 172.69.79.116
11 * * * Request timed out.
12 107 ms 106 ms 105 ms 103.168.172.65

Trace complete.

That took ages. Firefox just times-out.

When I go there I get l pointed to www.fastmail.com/?domain=justemail.net

justemail.net is now successfully loading to https://app.fastmail.com/login/?domain=justemail.net .

However, traceroute is still failing to trace the route.

Weird

Indeed! It must be going through some kind of concentrator when using the network path from your ISP, which is deliberately blocking UDP commands (possibly for DDoS protection).. Anyway, glad the redirect is now working correctly.

An early post in this thread mentions the secure version: https://www.justemail.net/
My browser hangs with no resolution of that URL.

But I can easily reach the insecure version: http://www.justemail.net
I am currently doing this while on a trip in the SF Bay area (Mountain View, CA) rather than in my normal home location in the Dallas TX area.

Bill

Well, that is truly weird! A few days ago, both https and http resulted in the correct redirect when accessed from my home in Bangkok Thailand. Now, I see the same behaviour you are describing.

It doesnt matter......

http://www.justemail.net puts me on
https://www.fastmail.com?domain=justemail.net

Are you a Fastmail customer? That’s what it’s supposed to do.

Fastmail owns many domains which may be used for account names (and email addresses).
https://www.fastmail.com/about/ourdomains/

You can use mail.justemail.net or www.justemail.net and it will redirect to the main Fastmail login screen with the domain name preloaded in the URL.This may make it slightly faster to log in.

Bill

Trying some of the other supported domains, both https and http work. I guess this could be a certificate problem, but I am puzzled as to why https:justemail.net worked for me a few days ago.

Well maybe because justemail.net is just forwarding to another domain they just use http...