Hi, it looks like https://freedium-mirror.cfd/ is not responding again.
I cloned and tested the latest repository:
text Repository: https://github.com/wywywywy/freedium-browser-extension.git
Branch: main
Local status: Already up to date
Extension name: Open in Freedium
Configured backend in background.js: https://freedium-mirror.cfd/
I also checked the origin/feat/new-url branch, but it still points to the same backend:
text https://freedium-mirror.cfd/
Network testing from my Mac shows that DNS resolves correctly and TLS handshake succeeds, but the HTTP request hangs with 0 bytes received until timeout.
Sample result:
bash curl -4 --http1.1 -I -L --max-time 20 https://freedium-mirror.cfd/
curl: (28) Operation timed out after 20002 milliseconds with 0 bytes received
I also tested from another network and got the same timeout. Public status checkers are also showing freedium-mirror.cfd / freedium.cfd as down or no response.
This seems like a fresh backend/mirror issue, not a local extension or clone issue.
Hi, it looks like https://freedium-mirror.cfd/ is not responding again.
I cloned and tested the latest repository:
text Repository: https://github.com/wywywywy/freedium-browser-extension.git
Branch: main
Local status: Already up to date
Extension name: Open in Freedium
Configured backend in background.js: https://freedium-mirror.cfd/
I also checked the origin/feat/new-url branch, but it still points to the same backend:
text https://freedium-mirror.cfd/
Network testing from my Mac shows that DNS resolves correctly and TLS handshake succeeds, but the HTTP request hangs with 0 bytes received until timeout.
Sample result:
bash curl -4 --http1.1 -I -L --max-time 20 https://freedium-mirror.cfd/
curl: (28) Operation timed out after 20002 milliseconds with 0 bytes received
I also tested from another network and got the same timeout. Public status checkers are also showing freedium-mirror.cfd / freedium.cfd as down or no response.
This seems like a fresh backend/mirror issue, not a local extension or clone issue.