I never had any problem with torrentgalaxy, but now, when going to the new domain I get an error (SEC_ERROR_UNKNOWN_ISSUER) related to the certificate, that no one seems to get. Anyone else in the same boat?
Working for me also, sure u have the right domain?
Yeah, that’s it. When I enter the old .to domain I get redirected to this one automatically, and it gives me the certificate error.
May be an issue with your browser certifications, or even isp block. Have you tried a vpn?
Sorry for the late reply! Today I tried to enter the site and everything works flawlessly without any change on my end, so everything is ok now! Thanks for your help, dude!
deleted by creator
It’s working fine for me. The onion site works fine too.
Coud you post the .onion link, please? I have no way to enter the site to look for it.
FYI all the official domains and .onion link are on their proxygalaxy page
For what it’s worth .to does not forward me to .mx, each of those domains seem to work fine on their own. Not sure what exactly is happening with your browser, maybe try clearing the cache / doing a hard reload.
I knew about the site, but I could not access it either. I’ve been AFK a couple of days, and without tinkering with anything, it’s all back to normal. Thank you for your help!
Thanks, everything is working well, now. I have no idea what happened but it’s over.
Just occurred to me that I could try the clearnet domain on Tor, and it works well. I don’t get what’s up with my Firefox installation, it doesn’t work in my profile nor in any new profiles.
Do you have DoH enabled in FF by any chance?
Yes, I do, but I don’t think it was because of this. It’s still enabled and now I don’t have any problems with the site. Do you think that it’s related to DoH?
Happens to me all the time. Exempt website from DoH, works like a charm. Remove exemption, doesn’t load.
Have you tried raising an issue in the mozilla forums or something like that? I enabled it when it came out and I don’t remember any problem that occurred because of it. Hope you can fix it!
There’s nothing to fix. DNS-Over-HTTPS is entirety at the mercy of the DNS server you add in the configuration. I’m using Mullvad’s I believe, so if something doesn’t resolve over their DNS, then it could be that they are either blocked or throttled in resolving the target.
Might sound stupid given that you seem much more knowledgeable than me regarding this matter, but have you considered changing resolvers or is that out of the question? Quad9 is a very reputable company (with which I’m not affiliated in any way), and as I said before, never had an issue with them.