3 ms·
Phone email client is trying imap.fastmail.com/2607:7700:0:1e:0:1:426f:488 and timing out. Now that I think about it, this started when I left the house/wifi. M
by public_defender 4y ago
Phone email client is trying imap.fastmail.com/2607:7700:0:1e:0:1:426f:488 and timing out. Now that I think about it, this started when I left the house/wifi. Must be something weird about the mobile network connection. I just switched carriers.
- LinuxBender 4y agoPerhaps your mail client cached the ipv4 and ipv6 when you were at home and your client is preferring ipv6. Try looking up the method to flush DNS cache for your make/model of phone and see if that helps. Perhaps a power-cycle would suffice.
- public_defender 4y agoI can't load the website by entering the IP (66.111.4.148) in my browser and can't ping it from termux. Weird.
- LinuxBender 4y agoTry turning airplane mode on/off, and/or disable wifi. You wont be able to load the site by IP either way. Also completely exit/terminate the fastmail app before doing any of this.
- public_defender 4y ago~ $ nmap 66.111.4.148 Starting Nmap 7.92 ( https://nmap.org https://nmap.org ) at 2022-11-05 17:12 EDT Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn Nmap done: 1 IP address (0 hosts up) scanned in 3.11 seconds ~ $ nmap 66.111.4.148 Starting Nmap 7.92 ( https://nmap.org https://nmap.org ) at 2022-11-05 17:17 EDT Nmap scan report for www.fastmail.com (66.111.4.148) Host is up (0.029s latency). Not shown: 997 filtered tcp ports (no-response) PORT STATE SERVICE 53/tcp open domain 80/tcp open http 443/tcp open https Nmap done: 1 IP address (1 host up) scanned in 4.96 seconds First time on mobile, second time on wifi.