-
Notifications
You must be signed in to change notification settings - Fork 629
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.
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
eturnal #2855
Conversation
@sando38 can you please check if the "" are correctly set in the config, please? |
An alternative is to As for the question regarding the |
and for the whitelist? |
do you think working with the downloaded tars works? |
no, that does not work, as they are compiled for glibc. We have not yet decided to publish the musl libc binaries. That is part of the review work. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
some comments/questions
29f5e31
to
bdb9455
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You probably want to change sed -i '/""/d' /opt/eturnal/etc/eturnal.yml
to sed -i '/""/d' /conf/eturnal.yml
as well.. or maybe even more smart, just use
$ETURNAL_ETC_DIR/eturnal.yml
everywhere. :)
thanks, fixed now |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Zoey2936 I just tested this and it seems like something does not work correclty when I try to join via the talk-android app. No video is shown and it just keeps spinning. I get these logs. Any idea?
|
no Idea, maybe @sando38 has an idea |
What are eturnal's log? |
Possibly we forgot to add the secret back? |
Ah no, it is there. So I guess I will need to test again and get the logs again... |
I've tested again and the same issue comes up again. After reverting this PR things start to work again.
|
If I read the problem correctly, the following seems to be the issue:
It seems like eturnal is not getting the correct ip-address of the android talk app? |
But this is weird because the browser on the other end of the connection seems to be correctly recognized:
|
These two eturnal log lines show the external client, which I guess it the IP address of your android talk app.
Now TURN allocations/sessions are created for the client
So from eturnal's point of view, it looks okay. This seems to be some networking topic in the end, but we will find out :)
|
It is the ipv4-address of the gateway of the nextcloud-aio network in which all AIO containers are.
yes, it is the ipv4-address of the nextcloud-aio-talk container which also includes the talk components
You mean if these ports are open on the server? I suppose not as only port 3478/tcp and 3478/udp is published from the container on the host...
port 3478/udp and 3478/tcp
It should be |
I see. The connection is established every
Here you posted a screenshot: It shows |
Ah you mean from the working setup, sorry I misread. the screenshot that I've posted was the one that coturn automatically figured out. So I suppose it should still be valid... (it should then probably be the ip-address of the talk container itself? Let me test...
|
Works 🎉 |
Fix is in #3217 |
Thank you very much @sando38 ! :) |
Address #2836