Skip to content

Add warning for IPV4 requirement in remote access #593

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
mmerklinger merged 4 commits into from
Jul 9, 2026
Merged

Add warning for IPV4 requirement in remote access #593

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
ea80d86
Add warning for IPV4 requirement in remote access
alexgithublab Jun 18, 2026
f327614
Update warning about remote access setup requirements
alexgithublab Jun 18, 2026
690f704
Fix syntax
mmerklinger Jul 9, 2026
d76e8f6
Incorporate review
mmerklinger Jul 9, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions source/components/nextbox/remote/index.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,6 +21,10 @@ If you struggle with the overall topic, please read:
scenarios the latter will also provide a better data bandwidth and user
experience*

.. warning::
If you don't have a full stack IPv4 the only possible method is the :doc:`Backwards Proxy <proxy>`.
For example LTE/5G routers may require this method.

Before you set up a remote access method you might want to read the
:doc:`comparison<method-comparison>` in order to understand
the trade-offs and capabilities of the different approaches:
Expand Down
Loading