Nextcloud Configuration

Question

I'm trying to use an EC2 instance to set up a nextcloud server to backup documents on my computer.

I've launched an instance using Ubuntu 24.04.3 LTS.  I installed the nextcloud snap package.

I'm doing a manual configure of nextcloud: sudo nextcloud.manual-install admin password
Then I check my default trusted domain: sudo nextcloud.occ config:system:get trusted_domains  and I get localhost.
So far, so good.

Then I add my computer's IP address, or what I think is my computer's IP address, I have a VPN, but I believe it's turned off, to the array of trusted domains: sudo nextcloud.occ config:system:set trusted_domains 1 value='ip_address'

Then I open my browser, I go to the public IP address of my EC2 instance.  I get the nextcloud opening screen, but then I get the warning that I'm not using a trusted domain.

I've tried various methods of verifying which IP address my computer is actually going out on.  I can't find the apache2 files which would verify the IP address that's not accessing nextcloud.

What am I missing?

re:Post Agent · Accepted Answer

It sounds like you're having an issue with the trusted domains configuration in your Nextcloud setup on EC2. The problem is likely related to how your EC2 instance is identifying the incoming connection.

When you access your Nextcloud instance via your browser using the EC2's public IP address, Nextcloud is seeing a different domain/IP than what you've configured in the trusted_domains setting. This is why you're getting the "not using a trusted domain" warning.

Here are some steps to troubleshoot and fix this issue:

1. First, try adding the public IP address of your EC2 instance to the trusted domains:
```
sudo nextcloud.occ config:system:set trusted_domains 1 --value="your_ec2_public_ip"
```

2. You might also need to add any domain name you're using to access the server:
```
sudo nextcloud.occ config:system:set trusted_domains 2 --value="your_domain_name"
```

3. To see what domain/IP Nextcloud is actually detecting, you can check the Nextcloud logs. For the snap installation, you can view logs with:
```
sudo snap logs nextcloud
```

4. If you're behind a proxy or load balancer, Nextcloud might be seeing the internal IP rather than your client IP. In this case, you might need to add the internal IP to trusted domains as well.

5. You can also try adding a wildcard to temporarily allow all domains while testing:
```
sudo nextcloud.occ config:system:set trusted_domains 3 --value="*"
```
(Note: This is not recommended for production use)

6. Verify your security group settings to ensure that HTTP/HTTPS traffic is allowed to your EC2 instance from your IP address.

After making these changes, restart the Nextcloud service:
```
sudo snap restart nextcloud
```

This should help resolve the trusted domain issue and allow you to access your Nextcloud instance properly.  
**Sources**  
[Unable to start/load apache2 on LightSail LAMP configuration | AWS re:Post](https://repost.aws/questions/QUMZyopL0ERIaMlvTv-_ZkHg/unable-to-start-load-apache2-on-lightsail-lamp-configuration)  
[Forwarding public ip to private ip in EC2 ( windows server) for an http/https listener . | AWS re:Post](https://repost.aws/questions/QU76Tl9P2iQQ-LIRa38Us4Dw/forwarding-public-ip-to-private-ip-in-ec2-windows-server-for-an-http-https-listener)  
[Struggling with Cloud Quest Networking Concepts Practice Lab | AWS re:Post](https://repost.aws/questions/QU1NcgaDJsTTOKu7_GCLcu8A/struggling-with-cloud-quest-networking-concepts-practice-lab)

User-3214243 · Answer

Step 1 was the solution.  Thank you so much.  I don't understand why you would add the IP address of the nextcloud server itself, but, it works.

Nextcloud Configuration

답변 추가

관련 콘텐츠