Certificate headache and more…

ℹ️ Support
1

Hi everyone,

I’ve been struggling for years to get a setup working with the following requirements, and I’m hoping someone here might have some insights:
• Fully on-premise setup
• A private LAN that only allows incoming VPN traffic (outgoing mostly unrestricted)
• Ability to create and edit Office documents using CODE
• Remote access to apps via VPN
• Access to Nextcloud in a browser within the LAN without certificate errors

Is this combination even possible? Or is there a proper way to handle the certificate situation, which seems to be the trickiest part?

Right now I have a Nextcloud instance running on Ubuntu, installed via Snap. So far, getting certificates to work properly has been a nightmare.

The biggest hurdle has been self-signed certificates—they never seem to work fully, especially not with CODE. I did manage to get it working briefly with a self-signed cert, but it seems to have broken again after a recent update.

At this point, I’m not sure how to move forward.
Has anyone here successfully set up something similar, or have any suggestions for how to tackle the certificate issue?

Thanks in advance!

2

nope… without DNS and a public certificate you’ll not get rid of your headache. See requirements especially network section.

self signed certificates will always cause browser-warning issues, that’s the way it works and CODE may work locally with a self signed certificate but not without browser warning issues either.

see managing encryption… there are no issues with that utility so your issue is presumably some sort of configuration thing…

wondering why people are hesitant to make their cloud accessible? no idea why air-gapped instances are required.

1 Like