Skip to content

Restoring a service from backup should preserve its previous external port #4208

Description

@dux-nine

Environment

  • StartOS version and git hash: not known (reported via support chat)
  • Area: backup/restore, networking (service interface external port)
  • Service: Nextcloud, restored from a StartOS backup; accessed on the LAN by IP address and port

What happens

After restoring Nextcloud from a StartOS backup, the service is served on a different external port than before the restore. The user connects all of their devices (desktop and mobile clients) by LAN IP address plus port, so every device's server address must now be updated, which is what they were trying to avoid by restoring.

There is no operator-facing way to set a service's external port back (see #3990), and the documentation does not say whether a restore preserves the assigned port. The cause has not been confirmed; the likely explanation is that the restore recreates the interface binding and allocates a fresh port, but that is an inference only.

What should happen instead

Restoring a service should return it to the configuration it had at the restore point, including each interface's previously assigned external port, or at least not change it. That port is typically saved in client apps and in router/tunnel rules.

Related: #3990 (operator-changeable external port), where a maintainer noted that nothing should move a service's port except the operator.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions