[Support] Linuxserver.io - Pydio


Recommended Posts

linuxserver_medium.png

 

Application Name: Pydio

Application Site: https://pyd.io/

Docker Hub: https://hub.docker.com/r/linuxserver/pydio/

Github: https://github.com/linuxserver/docker-pydio

 

Please post any questions/issues relating to this docker you have in this thread.

 

If you are not using Unraid (and you should be!) then please do not post here, instead head to linuxserver.io to see how to get support.

Edited by linuxserver.io
Link to comment
  • 2 months later...
  • 1 month later...

Thank a lot for this one. I'm still learning on the go, please be gentle. With the first run of Pydio (Pydio Diagnostic Tool) I get the following warning:

Php command line not detected, this is NOT BLOCKING, but enabling it could allow to send some long tasks in background. If you do not have the ability to tweak your server, you can safely ignore this warning.

I'm running the Apache docker.

 

Any ideas how to get rid of this warning?

 

Thanks again!

 

Happy New Year

Link to comment
  • 4 weeks later...

I'm not able to connect to the WebUI for Pydio.

I get a blank screen in Firefox, and a "Server Error 500" if I bring up the webUI in Chrome.

 

Is there any more configuration that needs to be done to the docker package (other then assigning /confg and /data)?

 

Looking at the docker logs file, this comes up every time I start the container.

We are now refreshing packages from apt repositorys, this *may* take a while

using keys found in /config/keys

Jan 28 21:42:33 17d5d2be9af2 syslog-ng[79]: syslog-ng starting up; version='3.5.3'

 

I've let it sit for hours in hopes the "refreshing packages" may take long, but still no web interface.

 

What can I do?

Link to comment

I deleted the container as you suggested, and now it gets stuck after refreshing all repositories.

 

Get:27 http://ubuntu.mirror.rafal.ca trusty/universe amd64 Packages [7,589 kB]
Get:28 http://ubuntu.mirror.rafal.ca trusty/multiverse amd64 Packages [169 kB]
Fetched 21.9 MB in 39s (557 kB/s)
Reading package lists...
using keys found in /config/keys
Feb 2 11:10:33 9d925c001327 syslog-ng[74]: syslog-ng starting up; version='3.5.3'
Feb 2 11:17:01 9d925c001327 /USR/SBIN/CRON[86]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)

Now it's stuck on "Reading package lists..."

 

I've removed the container (and cleaned app data) twice now, and each time it gets stuck in the same place.

Any other thoughts/suggestions?

Link to comment

I deleted the container as you suggested, and now it gets stuck after refreshing all repositories.

 

Get:27 http://ubuntu.mirror.rafal.ca trusty/universe amd64 Packages [7,589 kB]
Get:28 http://ubuntu.mirror.rafal.ca trusty/multiverse amd64 Packages [169 kB]
Fetched 21.9 MB in 39s (557 kB/s)
Reading package lists...
using keys found in /config/keys
Feb 2 11:10:33 9d925c001327 syslog-ng[74]: syslog-ng starting up; version='3.5.3'
Feb 2 11:17:01 9d925c001327 /USR/SBIN/CRON[86]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)

Now it's stuck on "Reading package lists..."

 

I've removed the container (and cleaned app data) twice now, and each time it gets stuck in the same place.

Any other thoughts/suggestions?

 

Is that log above from the first startup following a fresh pull from dockerhub and a clean appdata?

 

I've never used this, but just pulled it to check, and after it gets the 28th mirror it then takes a long time on the initial setup (like 30 mins or so) where it creates and inflates pydio and this is reflected in activity in the logs.  If the container were to be stopped or restarted during this initial setup then I suspect it would fail on subsequent starts.

 

As you can see from the excerpt of my log below, on first start up keys are generated, whereas in your log it is using keys already present.

 

-------------------------------------
_ _ _
| |___| (_) ___
| / __| | |/ _ \ 
| \__ \ | | (_) |
|_|___/ |_|\___/
|_|

Brought to you by linuxserver.io
We do accept donations at:
https://www.linuxserver.io/donations
-------------------------------------
GID/UID
-------------------------------------
User uid: 99
User gid: 100
-------------------------------------

finding fastest mirror
1. archive.ubuntu.com
Latency: 18 ms
Org: Canonical Ltd.
Status: Up to date
Speed: 100 Mbps
2. mirror.as29550.net
Latency: 19 ms
Org: XILO Communications Ltd.
Status: Up to date
Speed: 1 Gbps
3. repo.bigstepcloud.com
Latency: 19 ms
Org: Bigstep Cloud LTD
Status: Up to date
Speed: 1 Gbps
New config file saved to /defaults/sources.list
We are now refreshing packages from apt repositories, this *may* take a while
Ign http://archive.ubuntu.com trusty InRelease
Get:1 http://archive.ubuntu.com trusty-updates InRelease [64.4 kB]
Get:2 http://archive.ubuntu.com trusty-security InRelease [64.4 kB]
Get:3 http://archive.ubuntu.com trusty Release.gpg [933 B]
Get:4 http://archive.ubuntu.com trusty-updates/main Sources [311 kB]
Get:5 http://archive.ubuntu.com trusty-updates/restricted Sources [5,219 B]
Get:6 http://archive.ubuntu.com trusty-updates/universe Sources [185 kB]
Get:7 http://archive.ubuntu.com trusty-updates/multiverse Sources [5,113 B]
Get:8 http://archive.ubuntu.com trusty-updates/main amd64 Packages [872 kB]
Get:9 http://archive.ubuntu.com trusty-updates/restricted amd64 Packages [23.4 kB]
Get:10 http://archive.ubuntu.com trusty-updates/universe amd64 Packages [434 kB]
Get:11 http://archive.ubuntu.com trusty-updates/multiverse amd64 Packages [14.1 kB]
Get:12 http://archive.ubuntu.com trusty-security/main Sources [129 kB]
Get:13 http://archive.ubuntu.com trusty-security/restricted Sources [3,920 B]
Get:14 http://archive.ubuntu.com trusty-security/universe Sources [37.9 kB]
Get:15 http://archive.ubuntu.com trusty-security/multiverse Sources [2,164 B]
Get:16 http://archive.ubuntu.com trusty-security/main amd64 Packages [517 kB]
Get:17 http://archive.ubuntu.com trusty-security/restricted amd64 Packages [20.2 kB]
Get:18 http://archive.ubuntu.com trusty-security/universe amd64 Packages [160 kB]
Get:19 http://archive.ubuntu.com trusty-security/multiverse amd64 Packages [4,643 B]
Get:20 http://archive.ubuntu.com trusty Release [58.5 kB]
Get:21 http://archive.ubuntu.com trusty/main Sources [1,335 kB]
Get:22 http://archive.ubuntu.com trusty/restricted Sources [5,335 B]
Get:23 http://archive.ubuntu.com trusty/universe Sources [7,926 kB]
Get:24 http://archive.ubuntu.com trusty/multiverse Sources [211 kB]
Get:25 http://archive.ubuntu.com trusty/main amd64 Packages [1,743 kB]
Get:26 http://archive.ubuntu.com trusty/restricted amd64 Packages [16.0 kB]
Get:27 http://archive.ubuntu.com trusty/universe amd64 Packages [7,589 kB]
Get:28 http://archive.ubuntu.com trusty/multiverse amd64 Packages [169 kB]
Fetched 21.9 MB in 46s (468 kB/s)
Reading package lists...
(Reading database ... 27760 files and directories currently installed.)
Preparing to unpack .../rsync_3.1.0-2ubuntu0.2_amd64.deb ...
Unpacking rsync (3.1.0-2ubuntu0.2) over (3.1.0-2ubuntu0.1) ...
Processing triggers for man-db (2.6.7.1-1ubuntu1) ...
Processing triggers for ureadahead (0.100.0-16) ...
Setting up rsync (3.1.0-2ubuntu0.2) ...
System start/stop links for /etc/init.d/rsync already exist.
generating self-signed keys in /config/keys, you can replace these with your own keys if required
Archive: install.zip
creating: pydio-core-6.2.2/
inflating: pydio-core-6.2.2/.htaccess 
inflating: pydio-core-6.2.2/base.conf.php 
inflating: pydio-core-6.2.2/cmd.php 
creating: pydio-core-6.2.2/conf/
inflating: pydio-core-6.2.2/conf/.htaccess 
inflating: pydio-core-6.2.2/conf/RELEASE_NOTE 
inflating: pydio-core-6.2.2/conf/VERSION 
inflating: pydio-core-6.2.2/conf/VERSION.php 
inflating: pydio-core-6.2.2/conf/bootstrap_conf.php 
inflating: pydio-core-6.2.2/conf/bootstrap_context.php 
inflating: pydio-core-6.2.2/conf/bootstrap_repositories.php

ETC ETC ETC ETC ETC

THEN

inflating: pydio-core-6.2.2/plugins/uploader.jumploader/i18n/conf/en.php 
inflating: pydio-core-6.2.2/plugins/uploader.jumploader/i18n/conf/fr.php 
inflating: pydio-core-6.2.2/plugins/uploader.jumploader/i18n/conf/it.php 
inflating: pydio-core-6.2.2/plugins/uploader.jumploader/i18n/conf/pt.php 
inflating: pydio-core-6.2.2/plugins/uploader.jumploader/jumploader_tpl.html 
inflating: pydio-core-6.2.2/plugins/uploader.jumploader/manifest.xml 
inflating: pydio-core-6.2.2/plugins/uploader.jumploader/plugin_doc.html 
creating: pydio-core-6.2.2/plugins/uploader.plupload/
inflating: pydio-core-6.2.2/plugins/uploader.plupload/class.PluploadProcessor.php 
creating: pydio-core-6.2.2/plugins/uploader.plupload/i18n/
creating: pydio-core-6.2.2/plugins/uploader.plupload/i18n/conf/
inflating: pydio-core-6.2.2/plugins/uploader.plupload/i18n/conf/de.php 
inflating: pydio-core-6.2.2/plugins/uploader.plupload/i18n/conf/en.php 
inflating: pydio-core-6.2.2/plugins/uploader.plupload/i18n/conf/it.php 
inflating: pydio-core-6.2.2/plugins/uploader.plupload/manifest.xml 
inflating: pydio-core-6.2.2/plugins/uploader.plupload/plugin_doc.html 
inflating: pydio-core-6.2.2/plugins/uploader.plupload/pluploader_tpl.html 
inflating: pydio-core-6.2.2/publicLet.inc.php 
inflating: pydio-core-6.2.2/rest.php 
inflating: pydio-core-6.2.2/runTests.php 
Feb 3 00:25:56 25cabb780cbb syslog-ng[557]: syslog-ng starting up; version='3.5.3'
Feb 3 00:39:01 25cabb780cbb /USR/SBIN/CRON[574]: (root) CMD ( [ -x /usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d /var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 $(/usr/lib/php5/maxlifetime))

Link to comment

I'm not able to connect to the WebUI for Pydio.

I get a blank screen in Firefox, and a "Server Error 500" if I bring up the webUI in Chrome.

 

Is there any more configuration that needs to be done to the docker package (other then assigning /confg and /data)?

 

Looking at the docker logs file, this comes up every time I start the container.

We are now refreshing packages from apt repositorys, this *may* take a while

using keys found in /config/keys

Jan 28 21:42:33 17d5d2be9af2 syslog-ng[79]: syslog-ng starting up; version='3.5.3'

 

I've let it sit for hours in hopes the "refreshing packages" may take long, but still no web interface.

 

What can I do?

 

I had the same issue and here's how i fixed it

 

1)

docker ps  (find out your Pydio container id and image name)

docker stop <container id>    (stop the container)

docker rm <containerid>  (remove the container)

docker rmi <imageid>  (remove the image)

 

2)

go to your /config delete the pydio folder

go to your /data delete that folders that was created by pydio

rm -rf "folder name"

 

3)

Restart your unraid host.  This is important, it didn't work for me without restarting, just so you noted.

 

4)

now add the container from fresh and it should work.

 

 

I was able to replicate it twice, let me know how it goes

Link to comment

How do you change the port mapping?  It seems when I change 443 to anything else,  my gui breaks.  Any ideas?

 

Can you post a screenshot of the docker edit page of the new settings you want to work?

 

 

chTAipQ.png

 

 

I want to change the default 443 to 4443,  443 is already in use by my firewall VPN login page.    I tried to change it twice,  and GUI will not display with the new port mapping.

Link to comment

...

3)

Restart your unraid host.  This is important, it didn't work for me without restarting, just so you noted.

...

I was able to replicate it twice, let me know how it goes

Yup I was able to get it working after rebooting the UnRaid server. 

Thank you for that critical piece of advice.

 

I wonder why that step is necessary.

Link to comment

...

3)

Restart your unraid host.  This is important, it didn't work for me without restarting, just so you noted.

...

I was able to replicate it twice, let me know how it goes

Yup I was able to get it working after rebooting the UnRaid server. 

Thank you for that critical piece of advice.

 

I wonder why that step is necessary.

Absolutely no idea, only thing I can think of is it forces a refresh of the mirrors.  But that's purely speculation.

Link to comment

...

3)

Restart your unraid host.  This is important, it didn't work for me without restarting, just so you noted.

...

I was able to replicate it twice, let me know how it goes

Yup I was able to get it working after rebooting the UnRaid server. 

Thank you for that critical piece of advice.

 

I wonder why that step is necessary.

 

Yah I don't know why the restart was needed,  it shouldn't be.  Glad it worked for you as well.

Link to comment

How to correctly configure the sharing option?

 

 

http://i.imgur.com/FbsNmz1.png

No idea, post how you've got your container folder mappings set up and I'll take a look later tonight when I get home from work...

 

 

FYI, I just installed it via your template,  didn't mess with any other settings that was mentioned in this article:

https://pydio.com/en/docs/kb/system/configuring-public-link-pydio-6

 

 

plz help me take a look at it

 

volume mapping:

http://i.imgur.com/oTazQ6x.png

 

 

Share Settings in Pydio:

http://i.imgur.com/HCqVGaf.png

Link to comment

How to correctly configure the sharing option?

 

 

http://i.imgur.com/FbsNmz1.png

No idea, post how you've got your container folder mappings set up and I'll take a look later tonight when I get home from work...

 

 

FYI, I just installed it via your template,  didn't mess with any other settings that was mentioned in this article:

https://pydio.com/en/docs/kb/system/configuring-public-link-pydio-6

 

 

plz help me take a look at it

 

volume mapping:

http://i.imgur.com/oTazQ6x.png

 

 

Share Settings in Pydio:

http://i.imgur.com/HCqVGaf.png

 

OK, I've never used Pydio and tbh I will not be using Pydio as I have no need for it.  We support the container not the underlying application, so I probably won't be able to take this any further than this post.  But your share settings in Pydio should not be set as /mnt/user/Pydio/public as in the container there is no /mnt/user/Pydio because it is a mapped folder and you have mapped it to /data

 

Following this logic /mnt/user/Pydio/public should be /data/public.

 

Always remember Linux is case sensitive too.

Link to comment

How to correctly configure the sharing option?

 

 

http://i.imgur.com/FbsNmz1.png

No idea, post how you've got your container folder mappings set up and I'll take a look later tonight when I get home from work...

 

 

FYI, I just installed it via your template,  didn't mess with any other settings that was mentioned in this article:

https://pydio.com/en/docs/kb/system/configuring-public-link-pydio-6

 

 

plz help me take a look at it

 

volume mapping:

http://i.imgur.com/oTazQ6x.png

 

 

Share Settings in Pydio:

http://i.imgur.com/HCqVGaf.png

 

OK, I've never used Pydio and tbh I will not be using Pydio as I have no need for it.  We support the container not the underlying application, so I probably won't be able to take this any further than this post.  But your share settings in Pydio should not be set as /mnt/user/Pydio/public as in the container there is no /mnt/user/Pydio because it is a mapped folder and you have mapped it to /data

 

Following this logic /mnt/user/Pydio/public should be /data/public.

 

Always remember Linux is case sensitive too.

 

 

I figured it out,  your comment helped.  Ty

 

What I found out was there was no 'public' folder inside the 'data' folder,  I had to manually create both the 'public' folder and .htaccess file, and edit it per Pydio documentation here

https://pydio.com/en/docs/kb/system/configuring-public-link-pydio-6

 

sharing is working good now.

 

 

However, i sometimes get "database is locked" error message,  i'm using sqlite3,  might switch up to mysql later on.

 

 

 

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.