Command missing to set HTTPS port

[jassonmc]

We can set the HTTP port with that:
snap set onlyoffice-ds onlyoffice.ds-port=8888

But there does not seem to to be one for HTTPS port.

Please add something similar like:
snap set onlyoffice-ds onlyoffice.ds-sport=4433

Cheers
jassonmc

[IcemanFlo]

I've got the same problem. Would be nice if the feature can be included in the upcoming release.

Cheers
Florian

[agolybev]

Hi, I don't think is a problem.
To my mind, it's normal to use a standard port for SSL connections. For example, popular online ssl tools don't recognize other port than 443. If your DS is behind a proxy you have to provide ssl connections there and use any custom HTTP port for DS.

[jassonmc]

With Snap it's probably a bit different.
I am running Snaps of Nextcloud and Onlyoffice DS on the same machine.
The App that needs a standard Port 443 is in that very common combo Nextcloud, while Nextcloud can internally talk through another port with Onlyoffice DS.

[agolybev]

@jassonmc, I think the right way was placed both servers behind a proxy server. But your argument is valuable.

[IcemanFlo]

I've the same use case as @jassonmc, putting the DS on the same machine as nextcloud. The onlyoffice-ds shall only be accessibly by the nextcloud, so i want to run nextcloud on 443 and onlyoffice-ds on a different https port.

[duderino416]

What people are asking for won't work because SSL works on 443, for SSL to work for ONLYOFFICE which is needed it needs 443 open and it needs to be using it. If your Nextcloud is HTTPS that is.

What you can do to run both on the same machine is put ONLYOFFICE inside of an LXC container and reverse proxy to it as if it was another machine using the Apache or NGINX solutions provided on the main site.

[jassonmc]

@duderino416
I am already running Nextcloud snap and Onlyoffice DS snap on the very same machine.
Onlyoffice DS uses in that case HTTPS port 443 and Nextcloud uses HTTPS port 444.
Works with self signed certificates and does what it should, no LXC needed, nor wanted.
I surely could also manually adjust the https port of Onlyoffice DS snap, but from my point of view it would be just logical to allow adjusting the https port, since http is possible as well via built in tools.
The snap would port wise be on par what Nextcloud offers with their snap, where you can easily adjust both ports.

[gilluc]

@jassonmc
i made it like you say (on the same 'snap' machine):

• nextcloud https via nextcloud.https-enable then modify https port to 444
• onlyoffice-ds restarted after self-signed certs, operating on port 443
  https on onlyoffice runs fine
  https on nextcloud:444 runs fine to
  BUT onlyoffice plugin in nextcloud does not accept any https address for onlyoffice!!
  ending with:
  HealthcheckRequest on check error: cURL error 60: SSL certificate problem: self signed certificate (see http://curl.haxx.se/libcurl/c/libcurl-errors.html)

Apache under nextcloud is expecting the same certificates as nginx under onlyoffice ???

thanks in advance.
gilles

[gilluc]

@jassonmc
I tried first:
`cp cert.pem /var/snap/nextcloud/current/certs
cp privkey.pem /var/snap/nextcloud/current/certs
snap restart nextcloud

cp cert.pem /var/snap/onlyoffice-ds/current/var/www/onlyoffice/Data/certs/onlyoffice.crt
cp privkey.pem /var/snap/onlyoffice-ds/current/var/www/onlyoffice/Data/certs/onlyoffice.key
rm /var/snap/onlyoffice-ds/current/var/www/onlyoffice/Data/certs/dh*
snap restart onlyoffice-ds
then cp onlyoffice.crt /var/snap/nextcloud/current/certs/cert.pem
cp onlyoffice.key /var/snap/nextcloud/current/certs/privkey.pem
snap restart nextcloud

cp onlyoffice.crt /var/snap/onlyoffice-ds/current/var/www/onlyoffice/Data/certs
cp onlyoffice.key /var/snap/onlyoffice-ds/current/var/www/onlyoffice/Data/certs
cp dhparam.pem /var/snap/onlyoffice-ds/current/var/www/onlyoffice/Data/certs
snap restart onlyoffice-ds
`
each time, https to nextcloud:444 and onlyoffice worked fine and plugin wont work with https://debian.local/ which work fine to onlyoffice in browser.

help!
gilles

[gilluc]

@jassonmc
both https access (nextclous and onlyoffice) work but
my chrome browser says "invalid certificate" no matter of the self-signed certificate i use (nextcloud one or onlyoffice one)

is there any clue to create a self signed certificate that works on my local machine?
gilles

[gilluc]

@jassonmc
using mkcert for windows to create certificate for my local server.
works as expected with https on onlyoffice (i got the green icon)
does not work on nextcloud as starting nextcloud snap seems to re-create the self signed certificate ... so removing my mkcert certificate...
gosh...

[jassonmc]

@gilluc
I copy/paste my internal notes I used to install on a vanilla CentOS 7 VM.
Only showing the most important steps though, omitting the cert creation process.
I went the standard route of creating a root CA, intermediate CA and finally the server cert from the intermediate CA. The root CA cert and intermediate CA cert went into the chain.pem file for Nextcloud. I'm not sure what you would insert into the chain.pem if you only have a self-signed single certificate, probably nothing, since there is no chain.

Unfortunately, using self-signed cert or a non-public CA cert makes the adjustments in the configs as explained below a necessity.

Hope that helps ;)

Nextcloud setup

snap install nextcloud
mkdir /var/snap/nextcloud/current/certs/custom/
chmod 700 /var/snap/nextcloud/current/certs/custom/
cp /root/CERT/pem_nextcloud/* /var/snap/nextcloud/current/certs/custom/
nextcloud.enable-https custom /certs/custom/cert.pem /certs/custom/privkey.pem /certs/custom/chain.pem
snap set nextcloud ports.http=888 ports.https=444

Adjust config for Nextcloud

vi /var/snap/nextcloud/current/nextcloud/config/config.php
'onlyoffice' =>
array (
'verify_peer_off' => TRUE,
),

snap restart nextcloud

Onlyoffice setup

snap install onlyoffice-ds
cp /root/CERT/onlyoffice.key /var/snap/onlyoffice-ds/current/var/www/onlyoffice/Data/certs/onlyoffice.key
cp /root/CERT/onlyoffice.crt /var/snap/onlyoffice-ds/current/var/www/onlyoffice/Data/certs/onlyoffice.crt
snap set onlyoffice-ds onlyoffice.ds-port=889

Adjust config for Onlyoffice

vi /var/snap/onlyoffice-ds/current/etc/onlyoffice/documentserver/default.json -> "rejectUnauthorized": false

snap restart onlyoffice-ds

[gilluc]

Thank you I will try... ⁣................. Gilles Lucato gilles@lucato.com ................ Télécharger BlueMail pour Android ​ Le 5 janv. 2020 à 22:10, à 22:10, jassonmc <notifications@github.com> a écrit:

…

@gilluc I copy/paste my internal notes I used to install on a vanilla CentOS 7 VM. Only showing the most important steps though, omitting the cert creation process. I went the standard route of creating a root CA, intermediate CA and finally the server cert from the intermediate CA. The root CA cert and intermediate CA cert went into the chain.pem file for Nextcloud. I'm not sure what you would insert into the chain.pem if you only have a self-signed single certificate, probably nothing, since there is no chain. Unfortunately, using self-signed cert or a non-public CA cert makes the adjustments in the configs as explained below a necessity. Hope that helps ;) # Nextcloud setup snap install nextcloud mkdir /var/snap/nextcloud/current/certs/custom/ chmod 700 /var/snap/nextcloud/current/certs/custom/ cp /root/CERT/pem_nextcloud/* /var/snap/nextcloud/current/certs/custom/ nextcloud.enable-https custom /certs/custom/cert.pem /certs/custom/privkey.pem /certs/custom/chain.pem snap set nextcloud ports.http=888 ports.https=444 # Adjust config for Nextcloud vi /var/snap/nextcloud/current/nextcloud/config/config.php 'onlyoffice' => array ( 'verify_peer_off' => TRUE, ), snap restart nextcloud # Onlyoffice setup snap install onlyoffice-ds cp /root/CERT/onlyoffice.key /var/snap/onlyoffice-ds/current/var/www/onlyoffice/Data/certs/onlyoffice.key cp /root/CERT/onlyoffice.crt /var/snap/onlyoffice-ds/current/var/www/onlyoffice/Data/certs/onlyoffice.crt snap set onlyoffice-ds onlyoffice.ds-port=889 # Adjust config for Onlyoffice vi /var/snap/onlyoffice-ds/current/etc/onlyoffice/documentserver/default.json -> "rejectUnauthorized": false snap restart onlyoffice-ds -- You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub: #27 (comment)

[gilluc]

Thank you so much, it works!!! ⁣................. Gilles Lucato gilles@lucato.com ................ Télécharger BlueMail pour Android ​ Le 5 janv. 2020 à 22:10, à 22:10, jassonmc <notifications@github.com> a écrit:

…

@gilluc I copy/paste my internal notes I used to install on a vanilla CentOS 7 VM. Only showing the most important steps though, omitting the cert creation process. I went the standard route of creating a root CA, intermediate CA and finally the server cert from the intermediate CA. The root CA cert and intermediate CA cert went into the chain.pem file for Nextcloud. I'm not sure what you would insert into the chain.pem if you only have a self-signed single certificate, probably nothing, since there is no chain. Unfortunately, using self-signed cert or a non-public CA cert makes the adjustments in the configs as explained below a necessity. Hope that helps ;) # Nextcloud setup snap install nextcloud mkdir /var/snap/nextcloud/current/certs/custom/ chmod 700 /var/snap/nextcloud/current/certs/custom/ cp /root/CERT/pem_nextcloud/* /var/snap/nextcloud/current/certs/custom/ nextcloud.enable-https custom /certs/custom/cert.pem /certs/custom/privkey.pem /certs/custom/chain.pem snap set nextcloud ports.http=888 ports.https=444 # Adjust config for Nextcloud vi /var/snap/nextcloud/current/nextcloud/config/config.php 'onlyoffice' => array ( 'verify_peer_off' => TRUE, ), snap restart nextcloud # Onlyoffice setup snap install onlyoffice-ds cp /root/CERT/onlyoffice.key /var/snap/onlyoffice-ds/current/var/www/onlyoffice/Data/certs/onlyoffice.key cp /root/CERT/onlyoffice.crt /var/snap/onlyoffice-ds/current/var/www/onlyoffice/Data/certs/onlyoffice.crt snap set onlyoffice-ds onlyoffice.ds-port=889 # Adjust config for Onlyoffice vi /var/snap/onlyoffice-ds/current/etc/onlyoffice/documentserver/default.json -> "rejectUnauthorized": false snap restart onlyoffice-ds -- You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub: #27 (comment)

[Buliwif]

Great, thank you !
It work like a charm a give us the avaibility to work both snap on the same machine.

However, for obvious reasons it would be helfull to access https://nexcloud.domain.tdl and not https://nextcloud.domain.tld:444
Is it impossible to change the Onlyoffice snap https port ?

[gilluc]

I didn't find a way to change it... ⁣................. Gilles Lucato gilles@lucato.com ................ Télécharger BlueMail pour Android ​ Le 15 janv. 2020 à 11:54, à 11:54, Buliwif <notifications@github.com> a écrit:

…

Great, thank you ! It work like a charm a give us the avaibility to work both snap on the same machine. However, for obvious reasons it would be helfull to access https://nexcloud.domain.tdl and not https://nextcloud.domain.tld:444Is it impossible to change the Onlyoffice snap https port ? -- You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub: #27 (comment)

[Buliwif]

The best way I find is to add a DNS entries pointing on the IP adress of my router, and define a NAT which translate 433 to 444.
Happy to find a different way than using a reverse proxy.
It works fine :)

[jassonmc]

I haven't found a way to adjust the port for https.
Since the Snap and its configs are immutable, meaning its running from a mounted Squashfs filesystem, which is read-only, there is no obvious way to alter it.

To me, this also the biggest draw back from the Snap technology; its super secure immutability makes it also super unflexible, since you cannot adjust any config, not even to fix something...

It would help tremendously, if there would be a way to serve an alternative file for one that's stored immutable on Squashfs. Something like Docker layering tech or similar.