Maintenance - 29-30th of September


#21

Hi all

Just wanted to say that I also get very frequent issues since the maintenance, using the cloud apps through the browser (Firefox).

Sometimes, I get:

# 504 Gateway Time-out
nginx/1.13.12

Other times, I get:

# Not Found
The requested URL /apps/news/ was not found on this server.
Apache/2.4.25 (Debian) Server at cloud.indie.host Port 80

And other times, the page loads but I end up with only the top bar and nothing underneath.


#22

me too… extremely slow for anything and sometimes time out.


#23

@blub @stragu I know the cloud has been very slow lately. I’m still investigating on what is the bottleneck here… I will change a few things in the coming days to improve the performances on the php and mysql side, we will see if it gets better.

Plus I’d like to change the docker image we use, for the php-fpm one + nginx, but that will come a bit later.

Ultimately we will move the database to SSD disks but that comes with a cost that we need to think about.

A bit more background on what is going on:
So the cloud gets slower and slower as time goes on, at one point the health checks that we have setup restarts the cloud.

There was an issue, with the nextcloud apache config when the cloud restarts, leading to:

# Not Found
The requested URL /apps/news/ was not found on this server.
Apache/2.4.25 (Debian) Server at cloud.indie.host Port 80

Unfortunately I missed this a few times as it doesn’t appear in the monitoring, cloud restarts and you can login but you can’t get access to the pages.
This should not happen anymore.

Then when the cloud restarts, everyone is trying to reach the cloud in the same time, so yep timeouts.

Why is the cloud getting slower and slower, I’m still not sure. I changed a few things on the backup which could cause this issue, every 24h it is scanning and backuping millions of files.


#24

Sunday 04.11.2018:
I already noticed 6 times (14:09 / 15:22 / 21:18 / 21:32 / 21:47 / 22:00) a ‘502 Bad Gateway - The server returned an invalid or incomplete response.’

Monday 5.11:
11:33
‘504 Gateway Time-out’


#25

Unfortunately I did not find time to look more into this issue.

We will spend some time this weekend with @pierreozoux to work on this. Obviously the migration did not go as planned and we are very sorry about all the inconvenience that it lead to. So Sunday we come back with some news and solutions (worst case would be to rollback to our previous setup).

As I already mentioned we are low on human resources at the moment, it has been a one man show for more than a year now. But we are at a stage that we can grow, an offer for to join IndieHost has just been published :). So things are going to be smoother in the coming months and I’ll be able to split the workload and focus the technical aspects. We are bit in a downtime before going a step further.

Again sorry about that. Sunday we come back with good news :wink:


#26

Is the issue with static websites supposed to be fixed? Mine is still not working (security issue with the https access to the website), although I can update files on the cloud.
Thanks,
M

Error message: “Este sitio usa Seguridad estricta de transporte de HTTP (HSTS) para especificar que Firefox sólo puede conectarse a él de modo seguro. Como resultado, no es posible añadir una excepción para este certificado.”