# Pydio Cells 2 caddy error

**URL:** <https://forum.pydio.com/t/pydio-cells-2-caddy-error/3835>\
**Category:** Pydio Cells\
**Created:** [April 28, 2021, 1:26pm UTC](https://forum.pydio.com/t/pydio-cells-2-caddy-error/3835 "2021-04-28T13:26:05Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Sebastien](https://avatars.discourse-cdn.com/v4/letter/s/f475e1/32.png) [@Sebastien](https://forum.pydio.com/u/Sebastien)\
**Post date:** [April 28, 2021, 1:26pm UTC](https://forum.pydio.com/t/pydio-cells-2-caddy-error/3835/1 "2021-04-28T13:26:05Z")

</div>

Hi everyone,

I install Pydio Cells2 on a Ubuntu 20.04 server, and i got some error when it running.  
On the interface I got a message “Connexion trouble” and in the caddy\_error.log i got some error like :  
8/Apr/2021:10:32:43 +0200 [ERROR 502 /public/plug/gui.ajax/res/build/PydioWorkspaces.min.js] context canceled  
28/Apr/2021:10:32:43 +0200 [ERROR 502 /public/plug/gui.ajax/res/build/PydioForm.min.js] context canceled  
28/Apr/2021:10:32:43 +0200 [ERROR 502 /public/plug/meta.user/js/build/ReactMeta.js] context canceled  
28/Apr/2021:10:50:20 +0200 [ERROR 502 /a/frontend/session] context canceled  
28/Apr/2021:11:31:38 +0200 [ERROR 502 /plug/gui.ajax/res/build/PydioHOCs.min.js] context canceled  
28/Apr/2021:11:32:01 +0200 [ERROR 502 /plug/editor.pdfjs/pdfjs/web/compatibility.js] context canceled  
28/Apr/2021:11:32:01 +0200 [ERROR 502 /plug/editor.pdfjs/pdfjs/web/l10n.js] context canceled  
28/Apr/2021:11:32:01 +0200 [ERROR 502 /plug/editor.pdfjs/pdfjs/web/debugger.js] context canceled

My pydio is complety down and i add to restart it.  
Any idea for those error ?  
Thank a lot 🙂

---

<div class="post-metadata">

**Author:** ![Sebastien](https://avatars.discourse-cdn.com/v4/letter/s/f475e1/32.png) [@Sebastien](https://forum.pydio.com/u/Sebastien)\
**Post date:** [April 29, 2021, 1:39pm UTC](https://forum.pydio.com/t/pydio-cells-2-caddy-error/3835/2 "2021-04-29T13:39:10Z")

</div>

I put some details about the server, it’s 8c 2.1GHz-2.7GHz, 32Go RAM  
When pydio is down i got the message “There was a timeout while serving the request…” and i had to reboot it.

---

<div class="post-metadata">

**Author:** ![bsinou](https://yyz2.discourse-cdn.com/flex032/user_avatar/forum.pydio.com/bsinou/32/476_2.png) [@bsinou](https://forum.pydio.com/u/bsinou)\
**Post date:** [April 30, 2021, 6:29am UTC](https://forum.pydio.com/t/pydio-cells-2-caddy-error/3835/3 "2021-04-30T06:29:43Z")

</div>

Hello,

this kind of error generally shows a resource issue. Given the specs of your server (that are more than enough if 1. you don’t have many other apps that exhaust it 2. you have a reasonable number of users), I would have a look on the DB side. Did you change the max connection parameter ?

Another idea, that might lead to this kind of issues:  
your server might have been running for a looooong time =\> you might have an old version.  
We improved things a lot in this direction lately (and fixed a few memory leaks) , so I would also advise you to upgrade to the latest 2.2.6 and see what happen.

If both diagnose are wrong, please provide more details 🙂

---

<div class="post-metadata">

**Author:** ![Sebastien](https://avatars.discourse-cdn.com/v4/letter/s/f475e1/32.png) [@Sebastien](https://forum.pydio.com/u/Sebastien)\
**Post date:** [April 30, 2021, 10:42am UTC](https://forum.pydio.com/t/pydio-cells-2-caddy-error/3835/4 "2021-04-30T10:42:31Z")

</div>

Thank for your answer @bsinou 🙂

I check and no i did’nt change the max\_connexion in mysql, what is the requirement for this parameter ?  
Is there other change to make in mysql for optimise ?  
I’m also going to upgrade in 2.2.6

Have a good day

---

<div class="post-metadata">

**Author:** ![system](https://canada1.discourse-cdn.com/flex032/uploads/pydio/original/2X/6/61f19fa52ec15fd4250db51aea351adba0e831fd.png) [@system](https://forum.pydio.com/u/system)\
**Post date:** [June 4, 2021, 10:42am UTC](https://forum.pydio.com/t/pydio-cells-2-caddy-error/3835/5 "2021-06-04T10:42:33Z")

</div>

This topic was automatically closed 35 days after the last reply. New replies are no longer allowed.
