Hang after startup? (docker) #80
-
Hello, But, I can't go further, I'm not able to access to the web-UI (la connection a échoué - Firefox ne peut établir de connexion avec le serveur à l’adresse 192.168.1.254:8901) Log of the container stop at "starting in Actix runtime", I don't know if it's OK!
I'have made tests with a complete api_proxy_config file and an empty one (like in log) and it doesn't change anything. config.yml seems OK:
Source:
The mapping file is the same as yours (càd parfait pour les chaines françaises!!!) Thanks by advance for your help, I have probably missed or misunderstand something. P.S: J'espère vraiment à arriver à le faire fonctionner, ça répond exactement à mes besoins! (byebye threadfin?) |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 4 replies
-
I am not sure but i think, if the server inside the container is bound to 127.0.0.1, the mapped port on the host 8901 will not work because the service is not accessible on the container's external network interface; it's only accessible on the container's loopback interface 127.0.0.1. I have 0.0.0.0 instead of 127.0.0.1. Can you try and tell me. Btw you should have a valid api_proxy.yml. |
Beta Was this translation helpful? Give feedback.
-
Hi
Hope you can help me! |
Beta Was this translation helpful? Give feedback.
-
Hi ypu are running in docker? The port for the default server has to match the port on which m3u filter is running. Default port is 8901. If you use this port you cant use another port. For external, in your case domain server, you need to have a proxy from your router to the m3u-filter server ip and port, or expose the port on the router. |
Beta Was this translation helpful? Give feedback.
-
The webui is only for viewing the content and searching,, not filtering. It is only for you to have an overview. The filter functionality is defined in the config files. |
Beta Was this translation helpful? Give feedback.
-
Thank you |
Beta Was this translation helpful? Give feedback.
I am not sure but i think, if the server inside the container is bound to 127.0.0.1, the mapped port on the host 8901 will not work because the service is not accessible on the container's external network interface; it's only accessible on the container's loopback interface 127.0.0.1.
I have 0.0.0.0 instead of 127.0.0.1.
Can you try and tell me. Btw you should have a valid api_proxy.yml.