tl;dr
I can’t get proxying and theming to work with Pico. Thank you.
EDIT 001 FWIW I’m using a Let’s Encrypt cert, and the “Intermediate” apache configuration recommended by Mozilla’s SSL config generator.
EDIT 002 I’ve since upgraded Nextcloud to v20.0.4. The issue persists.
(…)
More
I’d like to use Pico CMS with Nextcloud, primarily so I can create a private site to use as a personal wiki.
I can
-
Create a test site and serve it at
https://mydomain.com/index.php/apps/cms_pico/pico_proxy/test001
-
Install themes by downloading them to
/path_to_nextcloud_data/appdata_<string>/cms_pico/themes
…But:
Problem #1: Proxying
I can’t serve the test site at https://mydomain.com/sites/test001
…and I don’t understand why; it’s not that complicated(?) I enabled the required modules, then added the following to the vhost (as per the instructions):
ProxyPass /sites/ https://mydomain.com/index.php/apps/cms_pico/pico_proxy/
ProxyPassReverse /sites/ https://mydomain.com/index.php/apps/cms_pico/pico_proxy/
SSLProxyEngine on
…then restarted apache. But it doesn’t work: the browser says
Proxy Error
The proxy server could not handle the request
Reason: Error during SSL Handshake with remote server
…and the apache error log confirms:
[proxy:error] [pid 430085] (20014)Internal error (specific information not available): [client aaa.bbb.ccc.ddd:ppppp] AH01084: pass request body failed to 127.0.0.1:443 (my domain.com)
[proxy:error] [pid 430085] [client aaa.bbb.ccc.ddd:ppppp] AH00898: Error during SSL Handshake with remote server returned by /sites/test001
[proxy_http:error] [pid 430085] [client aaa.bbb.ccc.ddd:ppppp] AH01097: pass request body failed to 127.0.0.1:443 (mydomain.com) from aaa.bbb.ccc.ddd ()
THINGS I’VE TRIED
a. Editing the vhost file: I tried
-
proxying to localhost, rather than “mydomain.com” (made no difference)
-
proxying to http, not https (unsurprisingly, this produced the browser error “The requested url was not found on this server”)
-
proxying to …cms_pico/pico/ (not …cms_pico/pico_proxy/ ) (made no difference)
-
adding additional apache directives:
SSLProxyVerify none
SSLProxyCheckPeerCN off
SSLProxyCheckPeerName off
SSLProxyCheckPeerExpire off
b. The things recommended in this thread: https://help.nextcloud.com/t/picocms-step-by-step-instructions-for-installation-and-configuration/22643/10
Problem #2: Theming
I can’t apply custom themes to sites: the ones I’ve installed are listed in the drop-down at Settings > Administration > Pico CMS > Custom themes (i.e. they’re apparently recognised as global config options)…but when I go to Settings > Personal > Pico CMS, only the default theme is available.
THINGS I’VE TRIED
a. Obvious stuff e.g. www-data has write permissions to the various folders
b. Symlinking the “themes” subfolder of the appdata folder to (various locations in) the corresponding nextcloud app folder
c. Copying the themes wholesale (instead of symlinking them)
d. The things recommended in this thread: https://help.nextcloud.com/t/applying-a-pico-cms-theme-any-theme/30791
Any help would be gratefully received!
P.S.
Nextcloud 20.0.3 stable
Pico CMS for Nextcloud 1.0.12 (Pico 2.1.4)
Apache 2.4.41
Ubuntu 20.04.1
P.P.S.
“Plan B” (which I’m considering at this point): use a different flat file markdown-based CMS, then incorporate it into Nextcloud using the External Sites app.