It has nothing to do with your email address in particular. As I said, it’s a problem of the mail server.
If you’re hosting the mail server by yourself, you need to track that error down on your server and check why there are so many SMTP connections.
The mail server you’re using has too many open connections and thus won’t send your email. Contact your email provider so that he can take a look at it.
Why don’t you just share this error? We cannot help you if we don’t know the error.
If you access the sitemap by yourself, is there any data?
Maybe it would help to remove and re-create the sitemap in the Google Webmaster Tools.
Sorry, my fault.
You need to enter the absolute URL to the sitemap.
Did you set a reCAPTCHA key in your administration control panel?
I didn’t seen it before: Your nginx configuration above seems not to apply to HTTPS connections since there is no HTTPS configured properly.
Please look at the nginx section here:
Do you mean above the menu or between menu and user panel?
This feature was available until WoltLab Suite 3 and has been removed due to “not enough usage and high code complexity”. I don’t think that it will be added again soon, even if I would love to see it.
No, you can either use one of them. I experienced that you don’t need reCAPTCHA if you use simple questions. Best spam blocking mechanism for me so far.
Ah okay, it just occurs if you reload the browser window in smartphone sizes. It seems that there is some Cloudflare extension enabled that adds and removes custom inline styles and thus breaks the layout. I don’t know much about Cloudflare so I think it would be better to create a ticket at the ticket support since Alexander Ebert knows the filters and functions of Cloudflare quite well.
Hm, I cannot reproduce the issue. At least not in Safari, Chrome and Firefox.
Do you have a link to the page where the problem occurs?
You could edit the template headInclude and remove the following line:
<meta name="viewport" content="width=device-width, initial-scale=1">
And tada, the mobile style is gone.
Is it really marked as error or just as info? I know at least one plugin that creates this kind of message but as the notice itself says: it just aborts. Nothing to worry here.
Is it even possible that you enabled the debug mode and that this message only occurs within the debug mode?
As far as I know, there is no such setting for users.
The easiest way would be in using different file names for different headers to force the cache to be reloaded.
You need to purchase an update first, as WoltLab Blog 2.1 won’t run with Burning Board 5.0 or WoltLab Suite Core 3.0.
