August 18, 20169 yr OK, so I had a quick play with this out of curiosity, out the box the api is accessible and the pydio client works. It appears that the change to the default file in the pydio appdata folder breaks the ability to reach the api. I'm going to try setting it up as https://pydio.server.com rather than https://server.com/pydio as I have a sneaky suspicion that will be the easiest way to proceed.
August 18, 20169 yr My suspicions were correct. Setting up a domain in the form of pydio.server.com and using the below config will work out the box with a fresh pydio install. So that's going to be my advice. It does tend to work better with apps like this and nextcloud. <VirtualHost *:80> ServerName pydio.server.com ServerAlias pydio.server.com DocumentRoot /config/www/ Redirect permanent / https://pydio.server.com/ </VirtualHost> <VirtualHost *:443> ServerName pydio.server.com ServerAdmin webmaster@localhost DocumentRoot /config/www/ SSLCertificateFile /config/keys/2_server.com.crt SSLCertificateKeyFile /config/keys/decryptedcertificatesigningrequest.key SSLCertificateChainFile /config/keys/1_root_bundle.crt SSLEngine on SSLProxyEngine On RewriteEngine On ProxyPreserveHost On SSLProxyVerify none SSLProxyCheckPeerCN off SSLProxyCheckPeerName off SSLProxyCheckPeerExpire off SSLProtocol -All +TLSv1 +TLSv1.1 +TLSv1.2 SSLCipherSuite ECDH+AESGCM:DH+AESGCM:ECDH+AES256:DH+AES256:ECDH+AES128:DH+AES:ECDH+3DES:DH+3DES:RSA+AESGCM:RSA+AES:RSA+3DES:!aNULL:!MD5:!DSS SSLHonorCipherOrder on <Location /> ProxyPass https://UNRAID-IP:HOST-PORT/ ProxyPassReverse https://UNRAID-IP:HOST-PORT/ </Location> </VirtualHost>
August 18, 20169 yr I've got the same error. I did a new install and made only the changes to get the reverse proxy working. With that working, I can use the web interface, but pressing the reload button on the browser causes it to fail and return a 404. Does anything special need to be done to Pydio to get it to work behind an Apache reverse proxy? Hi All, I just got Pydio up and running on my LAN. I also just set up a reverse proxy using Apache with SSL for all of my apps and it is working for couchpotato and sickrage. I really do not know much Apache beyond the tutorials I followed. I cannot get Pydio to work with my reverse proxy so when I go to mydomain.com/pydio I get a 400 error (sent http request to https port) Here is my apache config for Pydio OK, here's how to reverse proxy pydio with our Apache container.... 1. Edit appdata/pydio/nginx/site-confs/default On line 3 change root /config/www/pydio; to root /config/www; 2. Edit appdata/apache/apache/site-confs/default.conf changing UNRAID-IP & HOST-PORT to match your configuration. RewriteRule ^/pydio$ /pydio/ [R] <Location /pydio> ProxyPass https://UNRAID-IP:HOST-PORT/pydio/ ProxyPassReverse https://UNRAID-IP:HOST-PORT/pydio/ </Location> 3. Restart both containers. So, I got the Pydio Webgui working through my apache reverse proxy! However, I am now trying to get Pydio Sync to work (on my mac) and it is obviously not working. I think it is because of the following. root /config/www/pydio; to root /config/www; But keep reading. I am using Pydios quickstart guide, but I dont understand how to follow them in relation to my setup. https://pydio.com/en/docs/v6/checking-apis Specifically, a2enmod rewrite AllowOverride All Where does that code need to be implemented? Pydio nginx? or my apache reverse proxy? Anyway, my .htaccess rules seem to be correct and I updated my RewriteBase line to reflect my mydomain.com/pydio reverse proxy setup. However, my setup still fails the simple rewrite check. "The basic check is to enter a workspace (e.g. https://domain.tld/pydio/ws-workspace-slug) and simply reload the page." So i deleted everything and started from scratch. In the config wizard I specified /pydio as my installation directory (which rewrites the .htaccess file) and everything was working fine on my internal IP address. It was passing the rewrite test. However, I then edited the nginx default config so that would work with my reverse proxy root /config/www/pydio; to root /config/www; and it no longer passed the rewrite test, however it did start working with my reverse proxy. So I am now stuck with something that either works with my reverse proxy and does not pass the rewrite test (and thus Sync does not work) or vice versa. Essentially I need help to make it work with the reverse proxy while not ruining all the rewrite rules that pydio has. Help
August 18, 20169 yr I've got the same error. I did a new install and made only the changes to get the reverse proxy working. With that working, I can use the web interface, but pressing the reload button on the browser causes it to fail and return a 404. Errr... Did you read my two posts above?
August 18, 20169 yr I didnt refresh the page before posting. I've been playing with it all morning. Thanks for your info I've got the same error. I did a new install and made only the changes to get the reverse proxy working. With that working, I can use the web interface, but pressing the reload button on the browser causes it to fail and return a 404. Errr... Did you read my two posts above?
November 3, 20169 yr Subject Attribute /C has no known NID, skipped *** Running /etc/my_init.d/70_get_the_app.sh... % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed Archive: install.zip End-of-central-directory signature not found. Either this file is not a zipfile, or it constitutes one disk of a multi-part archive. In the latter case the central directory and zipfile comment will be found on the last disk(s) of this archive. unzip: cannot find zipfile directory in one of install.zip or install.zip.zip, and cannot find install.zip.ZIP, period. mv: cannot stat ‘pydio-*/data/*’: No such file or directory mv: cannot stat ‘pydio-*’: No such file or directory chown: cannot access ‘/config/www/pydio’: No such file or directory *** /etc/my_init.d/70_get_the_app.sh failed with status 1 *** Killing all processes... Fresh install doesn't work for me
November 4, 20169 yr I think Pydio have reconfigured their servers so it's not pulling the app anymore.
November 10, 20169 yr What should I put on Detected Server Path during installation? Leave it as it is.
November 21, 20169 yr Hey everyone, I have just installed the pydio docker, but I also have the Nginx-Letsencrypt already installed. Is there a way to change pydio to use the Nginx-letsencrypt rather than the one that came in the pydio docker?
November 21, 20169 yr Essentially two options: 1. Reverse proxy pydio with the letsencrypt container (would be my choice) 2. Manually install pydio not using this container at all, into the Nginx install of LetsEncrypt. Sent from my LG-H815 using Tapatalk
November 21, 20169 yr OK, so change the pydio container port to say, 4444, then block that port on the router, then modify the nginx-letsencrypt server block to proxy_pass to the IP and port 4444?
November 22, 20169 yr OK, so change the pydio container port to say, 4444, then block that port on the router, then modify the nginx-letsencrypt server block to proxy_pass to the IP and port 4444? Yep, although word of warning, I'd strongly suggest running this on it's own subdomain like pydio.server.com rather than server.com/pydio
January 25, 20179 yr I had some trouble with my Unraid/Pydio install and the "Pydio blank screen of nothingness". So wanted to post how I fixed it and maybe someone else can use the information. The short back story... My Nginx reverse proxy to Pydio installation was not always "stable". Different browsers gave me different problems, googled some fixes and it was suggested to log into Pydio and change the Server URL under the "Pydio Main Options' to fix it. It did not. Now every time I tried to connect got a blank screen. No Pydio log errors, no Nginx log errors, just nothing. I tried uninstalling and reinstalling the docker 4 times (with Unraid restarts), no bueno. Hindsite - Don't change the Server URL! The Fix... I'm using the MySQL and Pydio dockers (thanks to those that created them!) First: Log into the MySQL docker: docker exec -it dockername /bin/bash Log into the dbase: mysql -u username -p "activate" the database for pydio: MySQL> use pydiodatabasename Delete the core.ajaxplorer line inside table ajxp_plugin_configs: MySQL> “delete from ajxp_plugin_configs where id = ‘core.ajaxplorer’;” Next: Log into the Pydio docker: docker exec -it dockername /bin/bash cd over to the "/data/cache/" folder and delete any ".ser" files Restart the Pydio docker It should be fixed now. Bonus Content... Aptalca has a great nginx-letsencrypt docker that creates free certs for SSL sites (like my Nginx/Pydio site). This may be in the support thread and I missed it, but pro tip: under the docker SUBDOMAINS container var, there should not be any spaces between the comas and subdomains. it should be like this: subdomain1,subdomain2,subdomain3. If you DO put spaces in there, it will create a cert for the first one, but not the subsequent ones in the list.
January 25, 20179 yr Bonus Content... Aptalca has a great nginx-letsencrypt docker that creates free certs for SSL sites (like my Nginx/Pydio site). This may be in the support thread and I missed it, but pro tip: under the docker SUBDOMAINS container var, there should not be any spaces between the comas and subdomains. it should be like this: subdomain1,subdomain2,subdomain3. If you DO put spaces in there, it will create a cert for the first one, but not the subsequent ones in the list. Only problem is aptalca has joined us, so dev on letsencrypt will be on the ls.io version going forward.
April 12, 20179 yr On 11/22/2016 at 0:01 AM, CHBMB said: Yep, although word of warning, I'd strongly suggest running this on it's own subdomain like pydio.server.com rather than server.com/pydio Hey CHBMB, I am back again and I am using the Letsencrypt nginx container. I have Pydio up and running on my subdomain files.garrettdowd.com, but SSL isn't working (it is working for other containers such as deluge and plex requests). I do NOT have any certificates setup specifically for Pydio and so I am not surprised that there are issues. Is there a way to configure the Letsencrypt Nginx server so that the browser will show Pydio as secure? Here is my config (not much to see other than the default) server { listen 80; server_name files.garrettdowd.com; return 301 https://$server_name$request_uri; } server { listen 443 ssl; root /config/www; index index.html index.htm index.php; server_name files.*; ssl_certificate /config/keys/letsencrypt/fullchain.pem; ssl_certificate_key /config/keys/letsencrypt/privkey.pem; ssl_dhparam /config/nginx/dhparams.pem; ssl_ciphers 'XXXXXXXXXXX' ssl_prefer_server_ciphers on; client_max_body_size 0; location / { #auth_basic "Restricted"; #auth_basic_user_file /config/nginx/.htpasswd; include /config/nginx/proxy.conf; proxy_pass https://192.168.0.4:44334; } EDIT: It appears that routing Pydio through the Letsencrypt nginx server also creates rewrite rule problems. Any idea on where to start solving this issue? I am failing the rewrite rule test described here https://pydio.com/en/docs/v6/checking-apis. (Refreshing is working, but https://domain.tld/pydio/api/my-files/ls/ and others are not working) I have a vanilla installation right now and haven't changed anything from defaults. EDIT 2: I have SSL working for Pydio now, but regardless of what I do I cannot get PydioSync to work. I have done countless fresh installs, I have tried different NGINX configurations, I have ensured the workspaces are syncable, and I have ensured that the .htaccess files is correct. Everything seems to work except PydioSync and the API call tests. If anyone has a working PydioSync example of running the Pydio docker though the Letsencrypt docker please let me know. Edited April 24, 20179 yr by ZipsServer
April 26, 20179 yr Having the same issue as femin as far as pydiosync is concerned. I had it working until update to 7.x version of pydio.
June 13, 20179 yr Can someone help me out with how to create a database in MariaDB for pydio? I am struggling. Jeffrey, try adding :3306 onto the end of your IP address. Make sure you've created a database called pydio (or whatever) and don't use mysqli Sent from my LG-H815 using Tapatalk Edited June 15, 20179 yr by ice pube
June 15, 20179 yr 12 minutes ago, CHBMB said: Try following the instructions for Nextcloud on our website, should work. I tried that, but when I enter in the MariaDB info into the Pydio wizard, it says "unknown database 'pydio;" I just set up a test nextcloud container and it worked fine. Which database option do I use in the pydio wizard?
June 15, 20179 yr 1 minute ago, CHBMB said: Dunno. Post me a screenshot of the setup screen or something. Attached.
Archived
This topic is now archived and is closed to further replies.