nextcloud / nextcloud/server

restrict outgoing connections (privacy, data protection, outbound traffic)

Open
#38,728 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

0. Needs triage enhancement security
Dominant language
PHP
Stars
36.9k
Forks
5.2k
Avg merge
2d 3h
Merged PRs (30d)
713

Description

For privacy, data protection and security reasons it can be helpful to strictly control outgoing connections.

I suggest a setting to disable outgoing connections.

Some granularity for the setting may be helpful too. So for example updates can still be received but other outgoing connections can be disabled.

 

Alternatively an overview of remote addresses would be helpful. So a firewall can be used to restrict connections to them.
I could not find such a list, except for this forum thread from 2018:

Which URLs+IPs needed for outbound traffic from Nextcloud-server?
https://help.nextcloud.com/t/which-urls-ips-needed-for-outbound-traffic-from-nextcloud-server/27637

 


 

How to use GitHub
  • Please use the 👍 reaction to show that you are interested into the same feature.
  • Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
  • Subscribe to receive notifications on status change and new comments.

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no files, tests, or entry points. First clarify whether the goal is an outbound-connection control setting, granular exceptions, or a documented list of remote addresses; done requires an agreed scope and acceptance criteria before implementation.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
backend, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.