QNAP reverse proxy solves the problem of Docker not supporting IPv6.

Jun 5, 2023#qnap #docker166

AI Translation

This post is translated from Chinese into English through AI.View Original

AI-generated summary

The article discusses how a person set up an Emby server for their elderly family member to watch TV on a local network, but needed to move it to a different location. They tried using IPv6 with DDNS but found that the port was only mapped for TCP4 and QNAP's Container Station and Virtual Switch did not support IPv6 mapping. They solved the issue by using QNAP's reverse proxy service. They added the domain name and set the target to localhost with a self-selected port.

Originally set up an Emby for the convenience of the elderly to watch TV. It was always on the local network without any problems. Recently, due to some reasons, it needs to be moved to another location. Considering that mobile supports IPv6, it was thought to be more convenient. However, it was found that the IPv6 + port of DDNS cannot be accessed.

After troubleshooting various mappings and ports, the Emby backend and directly entering IPv6 could not solve the problem. Finally, it was found that the port only mapped TCP4, and QNAP's Container Station and Virtual Switch do not support enabling V6 mapping within Docker. Originally planned to use HAProxy or socat for forwarding, but finally temporarily solved it through QNAP's built-in reverse proxy.

Open QNAP's control panel and find the proxy service settings, switch to the reverse proxy tab, and add it. The domain name can use DDNS, and the target should be set to localhost. The port can be set as desired.

Control panel settings
Detailed settings for adding