nitter.net has disappeared

[thutt]

This isn't an issue with nitter software, but I'm getting the following:

Hmm. We’re having trouble finding that site.
We can’t connect to the server at nitter.net.

When attempting to navigate to Twitter's user pages via nitter.net.

Comparatively, has the DNS registration disappeared? (The registration is valid until 2024.08.06, according to a whois lookup)

nslookup twitter.com

Non-authoritative answer:
Name: twitter.com
Address: 104.244.42.65
Name: twitter.com
Address: 104.244.42.1
Name: twitter.com
Address: 104.244.42.129
Name: twitter.com
Address: 104.244.42.193

nslookup nitter.net

Non-authoritative answer:
*** Can't find nitter.net: No answer

[zedeus]

nitter.net is unavailable because Njalla (domain vendor) suspended my account. I'm waiting for them to respond.

[awsms]

nitter.net is unavailable because Njalla (domain vendor) suspended my account. I'm waiting for them to respond.

Thx for the quick answer, I was a bit worried as the website hasn't been available for the whole day

[gigirassy]

Hope this gets resolved!

[lukefromdc]

We need to know if Twitter is whining to domain vendors about Nitter instances.

[retry-the-user]

in the meantime add 185.246.188.57 nitter.net to your hosts file and you can still use it

[lukefromdc]

That gets a login request on an otherwise blank/white page

[jrfondren]

That IP works. You can't, however, go to https://$ip/ as that'll cause your browser to send the IP in the Host: header, which means the server won't dispatch the request to nitter.net. You need to do something like add it to your hosts file.

[retry-the-user]

Do you people not read? "in the meantime add 185.246.188.57 nitter.net to your hosts file and you can still use it"

add
to your hosts file

[jrfondren]

Someone without a relatively thorough understanding of webhosting will go to https://$ip/, get an error, and then conclude that the IP is wrong. Since the IP is wrong, why go to the effort of modifying a hosts file to something wrong?

Anything related to name resolution you'll just have to explain three times.

[lukefromdc]

When using DNS over HTTPS in Firefox, /etc/hosts is ignored by the browser. I consider this a nuisance side effect of forcing any ISP surveillance to use raw IP addresses and look them up themselves (which automated snooping may not bother with) as it makes blocking things like Facebook, Google, and their embedded content more difficult.

[lukefromdc]

How do I stop Firefox from redirecting 185.246.188.57 to https://185.246.188.57 with DNS over https engaged? Also I finally got Firefox to at least show just the IP address in the address bar but got error 401 "authorization required."

Webhosting I know little about, BTW. EDIT: same with browsers, mostly I know how to block things like trackers and ad networks, and not to use Chrome for anything,.

[jrfondren]

1. use another nitter instance that's still up
2. use another browser that the hosts file works for (Brave is one)
3. use your own DNS server and change your router or your computer to use it. A DNS server is a likely component of anti-adware solutions that work outside the browser, like a pihole.
4. use a public/alternate DNS service that supports edits (I don't know of any)
5. clone nitter, add in a new feature to have it proxy requests to an existing nitter server, plug the IP into that, and then make a pull request to add this as a normal feature. This way people can hit localhost without having to duplicate the elaborate auth system that's required now
6. run nitter locally with your own twitter creds

[jarrodmoldrich]

@lukefromdc In Firefox, I believe you can set network.trr.exclude-etc-hosts to true in about:config. You may have to add the relevant domains to network.trr.excluded-domains also, but I didn't need to.