winniewangyh 2 Posted December 17, 2024 Posted December 17, 2024 I deployed Emby on a QNAP NAS using Docker, but due to the Great Firewall (GFW), Emby is unable to scrape actor data properly. How can I correctly configure a proxy for the Docker version of Emby, either HTTP or SOCKS?
Luke 42077 Posted December 17, 2024 Posted December 17, 2024 HI, are you able to configure a proxy on the entire docker container?
winniewangyh 2 Posted December 17, 2024 Author Posted December 17, 2024 I configured a proxy in QNAP QTS Hero OS but did not configure it in the Docker application.
winniewangyh 2 Posted December 17, 2024 Author Posted December 17, 2024 3 hours ago, Luke said: 你好,您能在整个 docker 容器上配置代理吗? I configured a proxy in QNAP QTS Hero OS but did not configure it in the Docker application
Luke 42077 Posted December 18, 2024 Posted December 18, 2024 4 hours ago, winniewangyh said: I configured a proxy in QNAP QTS Hero OS but did not configure it in the Docker application Are you able to do that?
winniewangyh 2 Posted December 21, 2024 Author Posted December 21, 2024 On 2024/12/18 at AM8点51分, Luke said: 你能做到吗? I configured the HTTP proxy environment for the Emby container like this, but it seems like it's not working environment: - HTTP_PROXY=http://192.168.1.140:7890 - HTTPS_PROXY=http://192.168.1.140:7890
Luke 42077 Posted December 21, 2024 Posted December 21, 2024 Hi, how did you determine that it's not working?
winniewangyh 2 Posted December 27, 2024 Author Posted December 27, 2024 On 12/22/2024 at 1:27 AM, Luke said: Hi, how did you determine that it's not working? Because the film scraping cannot be carried out normally.Then I changed the nas gateway to point it to my other router。But today I found a new problem, I can not access my emby server normally, it is always stuck on the screen of the logo, whether it is external network or internal network. This is the startup log of docker, but there seems to be nothing wrong log.txt
Luke 42077 Posted December 27, 2024 Posted December 27, 2024 6 hours ago, winniewangyh said: Because the film scraping cannot be carried out normally.Then I changed the nas gateway to point it to my other router。But today I found a new problem, I can not access my emby server normally, it is always stuck on the screen of the logo, whether it is external network or internal network. This is the startup log of docker, but there seems to be nothing wrong log.txt 7.9 kB · 0 downloads HI, are you sure that is the complete log file? That does not look like a normal Emby Server log.
JohnFury 0 Posted May 22, 2025 Posted May 22, 2025 I had a similar issue setting this up behind my reverse proxy, and what helped was checking the headers and making sure the real IP was coming through. If you're still getting weird behavior or rate limits, I’d recommend you Buy Datacenter Proxies to keep things smoother and avoid detection issues, especially if you're using automated access or multiple users from different locations.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now