How to deploy inside Portainer or in a containerized environment with SSL #1666
-
|
Hello OME team, We use your product and love it! We have one question regarding the Server.xml file inside the conf. directory. We have put the certs files and kept the Server.xml like below: Nevertheless, we cannot use the API when curling to https://{our_domain}/v1/stats/current/vhosts/test By the way, here is the cmd that we use to send the stream:
|
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 18 replies
-
|
There will be a hint in the log. If you upload the log file and the entire Server.xml, I will check it. |
Beta Was this translation helpful? Give feedback.
-
|
iam new |
Beta Was this translation helpful? Give feedback.
-
Sure I will try to track the cert part in the full logs and send you the log. Will send you this tomorrow morning. To answer your question : the certs were not there initially, but placed after by our DevOps. And I believe this is the root cause of the issue. Will check that tomorrow, thks ! If it is the cause, is there a way to restart the ome server inside the container without restarting the whole container ? Or a way maybe to dynamically update the cert configuration of the ome when it is already running? |
Beta Was this translation helpful? Give feedback.
-
|
Please find attached the full logs |
Beta Was this translation helpful? Give feedback.
-
|
certs loading are ok from what I see from the logs here: |
Beta Was this translation helpful? Give feedback.
-
|
When I start streaming it seems ok from the log I get from the docker container: But I am unable then to target the stream using wss:
|
Beta Was this translation helpful? Give feedback.
-
|
My next guess is the docker container's ports are not accessible for
whatever reason. Can you post your docker run command or compose file
…On Sun, Jul 21, 2024 at 06:13 antonymarion ***@***.***> wrote:
When I start streaming it seems ok from the log I get from the docker
container:
image.png (view on web)
<https://github.com/user-attachments/assets/3288ee4a-c860-4027-a080-1b9249a42d6a>
But I am unable then to target the stream using wss:
image.png (view on web)
<https://github.com/user-attachments/assets/f2509370-1898-480b-aeaf-41fe7c637eda>
—
Reply to this email directly, view it on GitHub
<#1666 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABV4BWPDF7YNN3EDUI7QAGDZNOCS7AVCNFSM6AAAAABLCL6R3OVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTAMJQGYYTANQ>
.
You are receiving this because you commented.Message ID:
***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
-
|
Sure, please find below the whole conf. from portainer:
|
Beta Was this translation helpful? Give feedback.
-
|
Ohhh it seems that 3334 port (SSL port for ws) is not open right ? so that's the reason I believe |
Beta Was this translation helpful? Give feedback.
-
|
Well, I added 3334 port binding between host and container (inside portainer conf.) and now I am getting the following console log on our https player:
|
Beta Was this translation helpful? Give feedback.
-
|
What does the OME log show?
…On Sun, Jul 21, 2024 at 5:45 PM antonymarion ***@***.***> wrote:
Well, I added 3334 port binding between host and container (inside
portainer conf.) and now I am getting the following console log on our
https player:
image.png (view on web)
<https://github.com/user-attachments/assets/a2a40ace-82f7-414f-839c-4797abf6d496>
—
Reply to this email directly, view it on GitHub
<#1666 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABV4BWMVL3LGGCFMDGBXNITZNQTYVAVCNFSM6AAAAABLCL6R3OVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTAMJQHA3TQNA>
.
You are receiving this because you commented.Message ID:
***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
-
|
Ome logs look good |
Beta Was this translation helpful? Give feedback.
-
|
Set the OME_HOST_IP environment variable to the IP address that the player can access. Your log has the following warning: Also, 0.16.7 does not work properly, although it is now removed. Check if it is 0.16.8. |
Beta Was this translation helpful? Give feedback.
-
|
If OME_HOST_IP isn't set, what happens? I don't think we have that set, and are looking to upgrade to 16.8 soon |
Beta Was this translation helpful? Give feedback.
-
|
If OME_HOST_IP is not set at all, it will work with the default setting, but in the above case, it will act as if Your.HOST.IP.Address is a domain, which may cause an error. In the case of default, OME will get all IPs from the NIC, use STUN to get IPs, and use all of them as candidates. In this case, the initial connection may be slightly slower because the Player will try all the candidates provided. This is also necessary because in cases like AWS, the public IP is not known inside the instance and Stun used by OME may not work. That's why we recommend OME_HOST_IP. |
Beta Was this translation helpful? Give feedback.
-
|
Indeed env var was missing, thks for your swift support guys! |
Beta Was this translation helpful? Give feedback.
If OME_HOST_IP is not set at all, it will work with the default setting, but in the above case, it will act as if Your.HOST.IP.Address is a domain, which may cause an error. In the case of default, OME will get all IPs from the NIC, use STUN to get IPs, and use all of them as candidates. In this case, the initial connection may be slightly slower because the Player will try all the candidates provided. This is also necessary because in cases like AWS, the public IP is not known inside the instance and Stun used by OME may not work. That's why we recommend OME_HOST_IP.