2 Pis each running Apache. Want to use existing domain to run Nextcloud with SSL certification

Troubleshooting
1

Creating a bug report/issue

I have searched the existing open and closed issues

Required Information

  • DietPi version | G_DIETPI_VERSION_CORE=8 G_DIETPI_VERSION_SUB=25 G_DIETPI_VERSION_RC=1 G_GITBRANCH='master' G_GITOWNER='MichaIng'
  • Distro version | echo $G_DISTRO_NAME $G_RASPBIAN
  • Kernel version | 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr 3 17:24:16 BST 2023 aarch64 GNU/Linux
  • Architecture | arm64
  • SBC model | Raspberry Pi 4
  • Power supply used | (Office power supply)
  • SD card used | Sandisk Ultra 128 GB

Additional Information (if applicable)

  • Software title | (Nextcloud)
  • Was the software title installed freshly or updated/migrated? Yes
  • Can this issue be replicated on a fresh installation of DietPi? Unknown
    ← If you sent a “dietpi-bugreport”, please paste the ID here →
  • Bug report ID | echo $G_HW_UUID

Steps to reproduce

  1. …
  2. …

Expected behaviour

  • …

Actual behaviour

  • …

Extra details

  • …

I have two Raspberry Pi’s each running Apache web server. My main Pi 3B+ is running https://chrisfoose.party.

I am running Nextcloud and other services on a Raspberry Pi 4. I want to be able to run the Nextcloud under the chrisfoose.party domain and have it SSL certified. I have experimented with HAproxy and I am not sure if it is working.

How can I go about solving this?

2

why are you opening an additional topic? DietPi multiple web servers & Nextcloud

Nothing to add on this new topic. Everything said on the other one.

you did not found your own topic? :thinking:

3

I never got a resolution.

4

and you never answered on my last post where I did some recommendation.

5

So the “main” servers runs on the RPi 3, there your apache listens on port 80 and 443. Also at your router/gateway you probably already forwarding port 80 and 443.

Then you need to set up a reverse proxy, so that when you hit https://chrisfoose.party it servers from the RPi3 but for e.g. https://chrisfoose.party/nextcloud it serves from the RPi4. There are plenty of guides online and also topics about this in this forum.
I assume you already have certificates made with cerbot, you can of course use them also for your reverse proxy, so that your proxied service can also use https.

What makes you unsure? I mean can you reach the nextcloud or not, it should be pretty unambiguous.

6

This topic was automatically closed 178 days after the last reply. New replies are no longer allowed.