Unsure, it normally indicates a server/iis problem, if you let me know when that error occurs I may be able to determine what might be the cause by looking in the server/iis logsOriginally posted by HuwR
I will
We have moved our email and changed our email server and now the forum doesn't send emails any more. I have changed the settings to the new smtp server. It still doesn't work. Host says I have to use a long and very strong password. And also
port 465 with SSL or
port 587 with STARTTLS / TLS
The problem is also that every second time I try to change anything, the forum goes down(!). "ERR_TOO_MANY_REDIRECTS"
So I can not easily change and try.
What does the different delivery methods mean in our admin email settings
? The old settings was 587 with delivery method network.
port 465 with SSL or
port 587 with STARTTLS / TLS
The problem is also that every second time I try to change anything, the forum goes down(!). "ERR_TOO_MANY_REDIRECTS"
So I can not easily change and try.
What does the different delivery methods mean in our admin email settings
? The old settings was 587 with delivery method network.
Posted
I will
Posted
Yes, but I wonder why we get these errors so often.Originally posted by Torborg
Unsure, it normally indicates a server/iis problem, if you let me know when that error occurs I may be able to determine what might be the cause by looking in the server/iis logs
Posted
Yes, but I wonder why we get these errors so often.
Posted
It gives that error because it is trying to reload the web site but encounters an error which it is unable to redirect to the error page so gets stuck in a loop. It is normally resolved by restarting the IIS AppPool or reversing any changes that were made or settings that were changed. Occasionally it requires an IIS Reset but not often.
Posted
Works now, with the code fix. Thanks!!
There have been a lot of down time lately, with the error "ERR_TOO_MANY_REDIRECTS". I wonder what that is.
There have been a lot of down time lately, with the error "ERR_TOO_MANY_REDIRECTS". I wonder what that is.
since it was a forum/IIS issue not a server issue