I'm also getting the 502 Bad Gateway error a few times a day, are there logs I can upload to help with nailing this bug down?

Any updates on this?

Any updates on this?

 

Not yet, this bug is proving to be difficult to debug.

Thank you at least for that update.

I did find this that seems like a possibility.

 

https://www.unixmen.com/how-i-fixed-nginx-502-bad-gateway-error/

Has anyone had any luck setting the 'overwritewebroot' flag to set a custom root? I'm try to set a custom root so I have something to filter on for my reverse proxy, but whenever I set that flag I get a "File not found: 404" in my browser and a line in the logs about a config file it can't find on a path that doesn't exist.

Whenever I try and do an update to the owncloud docker, it tries to update my database and just gets stuck on the page that says:

 

"This ownCloud instance is currently being updated, which may take a while.

This page will refresh itself when the ownCloud instance is available again."

 

I'm using a mariadb docker with this.

 

Any ideas?

Tony

Hi,

 

Update was good.  Using mariaDB backend, I just update using "Check for updates" on docker page of Unraid. 

 

It's working great.  You might install a new version of ACPu inside your docker file because it now report that inside the "Administration" portion of owncloud :

 

APCu below version 4.0.6 installed

APCu below version 4.0.6 is installed, for stability and performance reasons we recommend to update to a newer APCu version.

Yes, I did the docker update and then when going back into owncloud, I get the upgrading database issue. It just stays there.

I have to reinstall everything from scratch each time (deleting docker appdata)

 

 

Hi,

 

Update was good.  Using mariaDB backend, I just update using "Check for updates" on docker page of Unraid. 

 

It's working great.  You might install a new version of ACPu inside your docker file because it now report that inside the "Administration" portion of owncloud :

 

APCu below version 4.0.6 installed

APCu below version 4.0.6 is installed, for stability and performance reasons we recommend to update to a newer APCu version.

 

This was the cause of php-fpm stalls: https://bugs.launchpad.net/ubuntu/+source/php-apcu/+bug/1374892

 

Whenever I try and do an update to the owncloud docker, it tries to update my database and just gets stuck on the page that says:

 

"This ownCloud instance is currently being updated, which may take a while.

This page will refresh itself when the ownCloud instance is available again."

 

I'm using a mariadb docker with this.

 

Any ideas?

Tony

 

Try this:

 

docker exec ownCloud sudo -u nobody -s /bin/bash -c "php /var/www/owncloud/occ upgrade"  

 

This will upgrade ownCloud from the terminal, and avoid the webgui timeouts.

Hi,

 

Update was good.  Using mariaDB backend, I just update using "Check for updates" on docker page of Unraid. 

 

It's working great.  You might install a new version of ACPu inside your docker file because it now report that inside the "Administration" portion of owncloud :

 

APCu below version 4.0.6 installed

APCu below version 4.0.6 is installed, for stability and performance reasons we recommend to update to a newer APCu version.

 

This was the cause of php-fpm stalls: https://bugs.launchpad.net/ubuntu/+source/php-apcu/+bug/1374892

 

Is there a way to fix that by a docker exec something to upgrade that package? or it's harmless?

 

Try this:

 

docker exec ownCloud sudo -u nobody -s /bin/bash -c "php /var/www/owncloud/occ upgrade"  

 

This will upgrade ownCloud from the terminal, and avoid the webgui timeouts.

 

Great - that fixed it!

Tony

Hi,

 

Update was good.  Using mariaDB backend, I just update using "Check for updates" on docker page of Unraid. 

 

It's working great.  You might install a new version of ACPu inside your docker file because it now report that inside the "Administration" portion of owncloud :

 

APCu below version 4.0.6 installed

APCu below version 4.0.6 is installed, for stability and performance reasons we recommend to update to a newer APCu version.

 

This was the cause of php-fpm stalls: https://bugs.launchpad.net/ubuntu/+source/php-apcu/+bug/1374892

 

Is there a way to fix that by a docker exec something to upgrade that package? or it's harmless?

 

It's a recommended package, not a required one, so I will remove it from the next update until Ubuntu put version 4.0.7 on the repository.

 

Try this:

 

docker exec ownCloud sudo -u nobody -s /bin/bash -c "php /var/www/owncloud/occ upgrade"  

 

This will upgrade ownCloud from the terminal, and avoid the webgui timeouts.

 

Great - that fixed it!

Tony

 

Nice, that goes to the FAQ.

Has anyone had any luck setting the 'overwritewebroot' flag to set a custom root? I'm try to set a custom root so I have something to filter on for my reverse proxy, but whenever I set that flag I get a "File not found: 404" in my browser and a line in the logs about a config file it can't find on a path that doesn't exist.

 

Along with my earlier question how do I turn off https forcing? I'm working on getting this setup behind my entire public facing reverse proxy with an actual signed cert I have, so I don't want nginx/owncloud creating and forcing https at this layer.

The update to 8.0.2 went well....as always but the 502 Bad Gateway error still persist or have I missed a workaround?

gfjardim:  Any progress on tracking down the Bad Gateway issue?

Has anyone had any luck setting the 'overwritewebroot' flag to set a custom root? I'm try to set a custom root so I have something to filter on for my reverse proxy, but whenever I set that flag I get a "File not found: 404" in my browser and a line in the logs about a config file it can't find on a path that doesn't exist.

 

Along with my earlier question how do I turn off https forcing? I'm working on getting this setup behind my entire public facing reverse proxy with an actual signed cert I have, so I don't want nginx/owncloud creating and forcing https at this layer.

 

In my latest update, I create a plain text service on port tcp 8001.

 

gfjardim:  Any progress on tracking down the Bad Gateway issue?

 

After my second update (removal of php5-acpu), I haven't experienced any 502/504 timeouts yet, so let's hope it has been fixed.

I updated earlier today and so far so good.....I haven't seen the issue pop up again.  Thank you for your efforts gfjardim.

 

Edit:  Gateway issue seems to be resolved.  It's been rock solid since I updated.  Thanks again!

Has anyone had any luck setting the 'overwritewebroot' flag to set a custom root? I'm try to set a custom root so I have something to filter on for my reverse proxy, but whenever I set that flag I get a "File not found: 404" in my browser and a line in the logs about a config file it can't find on a path that doesn't exist.

 

Along with my earlier question how do I turn off https forcing? I'm working on getting this setup behind my entire public facing reverse proxy with an actual signed cert I have, so I don't want nginx/owncloud creating and forcing https at this layer.

That's exactly what I'm trying to do with smdion's apache reverse proxy docker.  Managed with just about everything else but own cloud has got me stumped.  Be interested to hear how you got reverse proxy working if you manage it.  I'm very new to web servers so a bit out of my comfort zone to be honest.

The 502 Bad Gateway error disappeared with the recent update!!! Thanks gfjardim!!!

Yes thank you very much.  I've been running error free for several days.

 

david

Thanks for the update.  No more 502 error!

Have you considered ownCloud in a docker container?  I highly recommend you look into that.

 

I took jonp's advice from a previous post and started to play around with ownCloud for the first time and I must say that it was fairly easy to install this docker. Thanks gfjardim for making this docker available.

 

Generally installing a docker application seems straight forward enough but while reading the previous posts and referring to ownCloud's documentation it seems as though a more robust database server can be used for ownCloud when using it for a large number of accounts and also for real time data syncing. I noticed that thegizzard had some initial issues with MariaDB and getting it to work with ownCloud and even though thegizzard seems to have worked out the issues with MariaDB and ownCloud there is very little documentation provided on how to proceed with the SQLite to MariaDB conversion. I have MariaDB installed but I can't go no further at this point as I have not idea how to access MariaDB config files to change Root password and to create the necessary account info for ownCloud. Even adding phpMyAdmin is a chore with no real guidance on how and where to install it. It would be of great help to others if the instructions on how to roll out MariaDB with ownCloud was posted.

 

 

I have no experience with owncloud and mariadb, but if you just want to set a root password in mariadb, you could connect from a different pc in your network with e.g. Heidisql and set the password.