Site can be accessed again (not solved by me).

Site can be accessed again.

Incident does not occur anymore now.

Me too, I am still frequently getting 503 errors.

The incident hasn't happened in the last days.

My experience as a daily user and editor: 1. often an 503 error and 2. slow performance

Several "503 Bad gateway" incidents last hour. After refresh (F5) however the requested wikipage is displayed.

503 Backend fetch failed about 12:50h UTC for wiki christipedia.miraheze.org

Yes, it works again. Today, after John's post of Oct. 16, I tried about six times to find a random image, of which one time it failed. When I reported the incident, I had tried several times. And also on days later on it did not work.

@Reception123 Yes, it was possible before. The problem is still there.

I solved the problem by assigning 'WriteAPI' to the user group "*". https://www.christipedia.nl/wiki/Speciaal:ManageWiki/permissions/*#mw-section-assigned

I made a new page and went than to the talk page of it. Adding a topic produces again the error:

This is what I mean by 'looks different':

After enabling the extension the interface of the talk page looked different. Adding a topic resulted in this error:

Second talk page gives the same error now (with disabled StructuredDiscussion/Flow extension):

Disabling the StructuredDiscussion/Flow extension results in this error on the talk page I use for testing purpose:

I reopenend the task. The error can easily be reproduced.

I confirm that the incidents do not occur anymore.

A seemingly related problem occurs with displaying some images on a page: they are not displayed on the page. they seem to not exist though inserted earlier. For instance, the first image on https://www.christipedia.nl/wiki/Vaccin.

Reopened this task as requested by Universal Omega.

Enabling the right "apihighlimit" does not solve the problem. I have disabled this right again.

I guess the incident has something to do with this issue: https://phabricator.wikimedia.org/T249705

Problem solved, not by erasing the cache, but by erasing in Google Chrome the browser history and the cookies.

Problem occurs with Google Chrome, no problem within Firefox

Yes, it is confirmed, it is working here!

Currently I get a certificate warning..

Great, noted and changed... nameserver are switched, thanks for the support!

Do you also have a third nameserver? My hoster is asking for that..

We made the switch, as usual this wil take some time to propagate

In T6529#128204, @Reception123 wrote:

It seems that your nameservers are still currently pointed at dns[123].vpshosting.nl.

Thanks @RhinosF1, when everything is sorted at your end, we know what to do!

That is even better! Could you please go for that solution. Which name servers should I use?

If that is possible yes, please! Could you provide the IP-address to refer to? Since a root-domain can't have a CNAME.

Unexpected wiki closure occured yesterday and today on Christipedia.miraheze.org. Both times I than reopened the wiki at https://christipedia.miraheze.org/wiki/Speciaal:ManageWiki/core

Solved by (1) activating the visual editor on https://christipedia.miraheze.org/wiki/Speciaal:ManageWiki/namespaces/2 and (2) than clearing de browsercache

Incident does not occur anymore. Thank you, Paladox.

I reopened the ask, because the incident is not solved on our wiki.

Incident keeps occuring.

Incident is back again. Two error messages: HTTP503 and HTTP500.

Incident does not occur anymore.

Incident solved

It works again on Christipediawiki. Thank you for solving the problem.

Incident solved after 1 minute.

Incident solved after couple of minutes

There are no longer such incidents.

I have the same issue with the visual editor. The error(s) appear in such a frequency that working with the visual editor has become uneasy and annoying. I get three types of error messages.

Error 503 Backend fetch failed, forwarded for 83.247.102.164, 127.0.0.1
(Varnish XID 557384484) via cp4 at Tue, 15 Oct 2019 21:18:48 GMT.

Short disruption:

Short disruption:

Error 503 Backend fetch failed, forwarded for 83.247.102.164, 127.0.0.1
(Varnish XID 200802307) via cp4 at Tue, 01 Oct 2019 16:45:10 GMT.

Shortly thereafter solved.