Opera redirects my site https://www.klimalex.de/ to 127.0.0.1 (disk cache)
-
Anonymous-Opera last edited by
Hello,
I operate the ecommerce website https://www.klimalex.de/.
On multiple independent Windows systems (including Windows 10 and Windows Server 2019), Opera Stable (versions 131.0.5877.24 and 131.0.5877.55) redirects my site to http://127.0.0.1, showing ERR_CONNECTION_REFUSED.
Observations:
- The site is reachable in Chrome, Firefox, and curl.
- curl with an Opera User-Agent correctly returns HTTP/1.1 200 OK and resolves to 178.250.9.119.
- DevTools Network in Opera shows:
- www.klimalex.de → 301 Moved Permanently (from disk cache)
- Next request → 127.0.0.1 → net::ERR_CONNECTION_REFUSED
- This affects multiple systems including VMs and external PCs.
Impact:
- This prevents Opera users from accessing a live ecommerce site.
- It seems Opera is using a cached permanent redirect incorrectly.
Attached screenshots show the error page, DevTools Network with 301 from disk cache, and curl outputs.
Steps already tried:
- Clearing Opera cache and site data
- Testing with a clean profile
- Multiple machines and Windows versions
Please investigate why Opera caches or applies this incorrect redirect to 127.0.0.1 and how this can be fixed.
Thank you.
-
leocg Moderator Volunteer last edited by@Anonymous-Opera When I try to open the page, I get:
Forbidden
You don't have permission to access this resource.Tried on Opera, Chrome, Edger and Vivaldi
-
Anonymous-Opera last edited by
@leocg
Thanks for testing.The “403 Forbidden” result is likely caused by our country/IP blocking rules, because we intentionally block traffic from several countries. If you are accessing the site from a blocked region, the 403 response is expected and is unrelated to the Opera-specific redirect issue.
If possible, please test again from a German IP address or via a VPN endpoint in Germany. The issue I am investigating is specifically this:
Chrome / Firefox / curl: website loads correctly
Opera Stable 131.x on Windows: redirects https://www.klimalex.de/ to http://127.0.0.1 from disk cacheSo your 403 result may be a separate access-control case.