[GH-ISSUE #51] No compatibility with Chrome and self-signed Cert #30

Closed
opened 2026-02-26 09:35:11 +03:00 by kerem · 4 comments
Owner

Originally created by @tautf on GitHub (May 18, 2017).
Original GitHub issue: https://github.com/ONLYOFFICE/Docker-DocumentServer/issues/51

Hey guys,

im not sure if this is a bug but it should be noticed anywhere.
I'm using Nextcloud and OnlyOffice Documentserver.

I generated self-signed certs for both systems.

When i try to open a document in my nextcloud im recieving the following error:
1111unbenannt

No errors where shown in the logs.
When i access my documentserver via browser and accept the following warning:
22222

The Documentserver says "Documentserver is running"

And now i can edit Files within my Nextcloud.

**Probably the error is shown because of the warning chrome shows when accessing a website with an invalid cert and because of this nextcloud cant connect to the documentserver.

With Firefox this is working**

Originally created by @tautf on GitHub (May 18, 2017). Original GitHub issue: https://github.com/ONLYOFFICE/Docker-DocumentServer/issues/51 Hey guys, im not sure if this is a bug but it should be noticed anywhere. I'm using Nextcloud and OnlyOffice Documentserver. I generated self-signed certs for both systems. When i try to open a document in my nextcloud im recieving the following error: ![1111unbenannt](https://cloud.githubusercontent.com/assets/18403881/26192308/75d22dfa-3bb1-11e7-8dea-99fbfe3d61b2.PNG) No errors where shown in the logs. When i access my documentserver via browser and accept the following warning: ![22222](https://cloud.githubusercontent.com/assets/18403881/26192316/7b4a5636-3bb1-11e7-8fc6-c9c90527729b.PNG) The Documentserver says "Documentserver is running" And now i can edit Files within my Nextcloud. **Probably the error is shown because of the warning chrome shows when accessing a website with an invalid cert and because of this nextcloud cant connect to the documentserver. With Firefox this is working**
kerem closed this issue 2026-02-26 09:35:11 +03:00
Author
Owner

@JohnPerkin commented on GitHub (May 18, 2017):

Hello @FlorianTaut !
We would recommend to use letsencrypt.org certificates instead of self-signed. Then Chrome will stop to take the connection as untrusted.

<!-- gh-comment-id:302337341 --> @JohnPerkin commented on GitHub (May 18, 2017): Hello @FlorianTaut ! We would recommend to use letsencrypt.org certificates instead of self-signed. Then Chrome will stop to take the connection as untrusted.
Author
Owner

@tautf commented on GitHub (May 18, 2017):

@JohnPerkin Yes would be possible, but not for internal usage. Letsencrypt doenst work for internal IP's.
This is just a Problem if you use it internal and access it via IP and not via f.e. office.domain.com for which you could request a SSL-Cert from Letsencrpyt.

<!-- gh-comment-id:302388922 --> @tautf commented on GitHub (May 18, 2017): @JohnPerkin Yes would be possible, but not for internal usage. Letsencrypt doenst work for internal IP's. This is just a Problem if you use it internal and access it via IP and not via f.e. office.domain.com for which you could request a SSL-Cert from Letsencrpyt.
Author
Owner

@thomass4t commented on GitHub (Apr 12, 2018):

You should create your certificates and sign it with one CA.
Import this CA into the windows cert-store --> trusted ceriticates (Vertrauenswürdige Stammzertifizierungsstellen).
This will prevent the warning in IE, Chrome and Edge.
The CA can also be distributed via GPO.
In FF it only works if you import your CA manually into the keystore of FF.

<!-- gh-comment-id:380774926 --> @thomass4t commented on GitHub (Apr 12, 2018): You should create your certificates and sign it with one CA. Import this CA into the windows cert-store --> trusted ceriticates (Vertrauenswürdige Stammzertifizierungsstellen). This will prevent the warning in IE, Chrome and Edge. The CA can also be distributed via GPO. In FF it only works if you import your CA manually into the keystore of FF.
Author
Owner

@ShockwaveNN commented on GitHub (Jul 10, 2019):

I'll close this issue, since it's pretty old
If issue still actual please create new issue

<!-- gh-comment-id:510049586 --> @ShockwaveNN commented on GitHub (Jul 10, 2019): I'll close this issue, since it's pretty old If issue still actual please create new issue
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/Docker-DocumentServer-ONLYOFFICE#30
No description provided.