Omega Owners Forum
Chat Area => General Discussion Area => Topic started by: zirk on 07 June 2020, 10:47:11
-
Http/1.1 Internal Server Error 43531
Been getting a lot of it recently, do reload then seems ok, my end ?
-
Only message I've been getting for ages is 'Not Secure' in the address bar.
-
Only message I've been getting for ages is 'Not Secure' in the address bar.
Well where you come from Steve, anything that isn't bolted down isn't Secure. ;D ;)
-
https://www.google.com/search?q=Http%2F1.1+Internal+Server+Error+43531&oq=Http%2F1.1+Internal+Server+Error+43531&aqs=chrome..69i57j69i58j69i61l2.5838j0j7&sourceid=chrome&ie=UTF-8
-
Only message I've been getting for ages is 'Not Secure' in the address bar.
Well where you come from Steve, anything that isn't bolted down isn't Secure. ;D ;)
I'm pretty sure that's racist, or something ;D
-
Only message I've been getting for ages is 'Not Secure' in the address bar.
Well where you come from Steve, anything that isn't bolted down isn't Secure. ;D ;)
I'm pretty sure that's racist, or something ;D
Nope, it's a celebration of cultural diversity :D
-
Http/1.1 Internal Server Error 43531
Been getting a lot of it recently, do reload then seems ok, my end ?
I'm not seeing that. If you are on a mobile carrier, which I know you often are, it could be related to the transparent proxies they put in the way?
The error number isn't valid for our software I don't think, you'd just get the standard, normal http error codes.
-
Only message I've been getting for ages is 'Not Secure' in the address bar.
Well where you come from Steve, anything that isn't bolted down isn't Secure. ;D ;)
I'm pretty sure that's racist, or something ;D
Racist no, Scousist. ;D
-
Http/1.1 Internal Server Error 43531
Been getting a lot of it recently, do reload then seems ok, my end ?
I'm not seeing that. If you are on a mobile carrier, which I know you often are, it could be related to the transparent proxies they put in the way?
The error number isn't valid for our software I don't think, you'd just get the standard, normal http error codes.
Hmm, yea EE, started having some other issues as well crop up. So I changed some of the EE APN Settings from ipv4 / ipv6 to ipv4 only.
Seems to have sorted it, for now, getting faster Web load times now as well, strange, but works.
-
OOF is currently IPv4 only*, and a lot of the dual stack setups are pseudo IPv4, either via a 6to4 or CGNAT or proxied. So always worth trying different options :y
We need to make the switch to IPv6, so I don't normally recommend disabling it... ...but sometimes, needs must etc.
*Well, it has a routable IPv6 but its incoming blocked at the firewall, and its AAAA record is for its real name, not www.omegaowners.com.