Installing SSL Certificate in Nextcloudpi

,

I hope someone can give me some help as I think I am a little out of my depth with the problem. I have a self hosted Nextcloudpi server installed from Github. Up until a few days ago all was fine then suddenly my Apple phone decided that some of the apps that I use can’t login due to the message “invalid certificate” MY old Samsung phone fine no issues just Apple. We live on a remote island in West Papua so the only communication is through Starlink and so using Let’sEncrypt won’t work. While away from the island I use Milrotik BTH tunnel. My problem is how do I get and install a certificate on my server? When I use the ls command I get as far as www but can’t access nextcloud files. Any help is greatly appreciated.

Support intro

Sorry to hear you’re facing problems. :slightly_frowning_face:

The community help forum (help.nextcloud.com) is for home and non-enterprise users. Support is provided by other community members on a best effort / “as available” basis. All of those responding are volunteering their time to help you.

If you’re using Nextcloud in a business/critical setting, paid and SLA-based support services can be accessed via portal.nextcloud.com where Nextcloud engineers can help ensure your business keeps running smoothly.

Getting help

In order to help you as efficiently (and quickly!) as possible, please fill in as much of the below requested information as you can.

Before clicking submit: Please check if your query is already addressed via the following resources:

(Utilizing these existing resources is typically faster. It also helps reduce the load on our generous volunteers while elevating the signal to noise ratio of the forums otherwise arising from the same queries being posted repeatedly).

Some or all of the below information will be requested if it isn’t supplied; for fastest response please provide as much as you can. :heart:

The Basics

  • Nextcloud Server version (e.g., 29.x.x):
    • replace me
  • Operating system and version (e.g., Ubuntu 24.04):
    • replace me
  • Web server and version (e.g, Apache 2.4.25):
    • replace me
  • Reverse proxy and version _(e.g. nginx 1.27.2)
    • replace me
  • PHP version (e.g, 8.3):
    • replace me
  • Is this the first time you’ve seen this error? (Yes / No):
    • replace me
  • When did this problem seem to first start?
    • replace me
  • Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
    • replace me
  • Are you using CloudfIare, mod_security, or similar? (Yes / No)
    • replace me

Summary of the issue you are facing:

[…]

Steps to replicate it (hint: details matter!):

Log entries

Nextcloud

Please provide the log entries from your Nextcloud log that are generated during the time of problem (via the Copy raw option from Administration settings->Logging screen or from your nextcloud.log located in your data directory). Feel free to use a pastebin/gist service if necessary.

PASTE HERE

Web Browser

If the problem is related to the Web interface, open your browser inspector Console and Network tabs while refreshing (reloading) and reproducing the problem. Provide any relevant output/errors here that appear.

PASTE

Web server / Reverse Proxy

The output of your Apache/nginx/system log in /var/log/____:

PASTE HERE

Configuration

Nextcloud

The output of occ config:list system or similar is best, but, if not possible, the contents of your config.php file from /path/to/nextcloud is fine (make sure to remove any identifiable information!):

PASTE HERE

Apps

The output of occ app:list (if possible).

Tips for increasing the likelihood of a response

  • Use the preformatted text formatting option in the editor for all log entries and configuration output.
  • If screenshots are useful, feel free to include them.
    • If possible, also include key error output in text form so it can be searched for.
  • Try to edit log output only minimally (if at all) so that it can be ran through analyzers / formatters by those trying to help you.

Why is that, no public ip?
There are other ways, that might be an option (DNS challenge):

If you work around something with letsencrypt it is free and still recognized by all major OS. Self-signed certificates are a different option, but then best is to install the certs directly on your devices.

Just checking, starlink provides ipv6 (https://www.starlink.com/support/article/1192f3ef-2a17-31d9-261a-a59d215629f4), if on the public DNS you use ipv6 only resolution, and letsencrypt should be possible with ipv6…

Thank you for your suggestions. Unfortunately with Starling we are not using ipv6 but ipv4 and so opening the ports 80 & 443 won’t work. I will look more into let’s Encrypt and see if there is a way around the problem.