Closed Chocobozzz closed 2 weeks ago
I'm not 100% that this is the issue. The diagnostic tool seems to point another issue. Have you another Peertube instance on the same server? If so, there are some ports to change in the plugin configuration. If not, can you check that there is no "prosody" process that was related to a previous peertube process, and that was not correctly killed? (i know this can happen in some case, but i did not find why yet).
Or maybe you don't have IPv6 on your server? (in this case, maybe your suggested fix is the correct one)
Have you another Peertube instance on the same server
No, it's the only instance
If not, can you check that there is no "prosody" process that was related to a previous peertube process, and that was not correctly killed? (i know this can happen in some case, but i did not find why yet).
Prosody ran by the livechat plugin is the only prosody process on the server
Or maybe you don't have IPv6 on your server?
The server has IPv6 enabled, and so localhost
can be resolved in a IPv6 address. However prosody is listening on 127.0.0.1:52800
The server has IPv6 enabled, and so
localhost
can be resolved in a IPv6 address. However prosody is listening on127.0.0.1:52800
Prosody configuration listen on both ipv4 and 6. Here are some parts of your diagnostic result:
interfaces = {
"127.0.0.1";
"::1";
};
c2s_interfaces = {
"127.0.0.1";
"::1";
};
http_interfaces = {
"127.0.0.1";
"::1";
};
https_interfaces = {
"127.0.0.1";
"::1";
};
trusted_proxies = {
"127.0.0.1";
"::1";
};
What makes you think Prosody only listen on ipv4? Have you tried telnet ::1 52800
?
Maybe have you a firewall?
I checked using ss
:
> % sudo ss -ltnp | grep 52800
LISTEN 0 128 127.0.0.1:52800 0.0.0.0:* users:(("lua5.2",pid=1405536,fd=8)
I don't know why prosody doesn't listen on ::1
too :thinking: Maybe the ;
should be ,
? https://prosody.im/doc/ports#ports
telnet ::1 52800
Yes, I confirm it doesn't work. (telnet 127.0.0.1 52800
works)
I don't know why prosody doesn't listen on
::1
too 🤔 Maybe the;
should be,
? https://prosody.im/doc/ports#ports
That's weird. Here is what i got on my server:
LISTEN 0 128 127.0.0.1:52800 0.0.0.0:* users:(("lua5.2",pid=1228702,fd=12))
LISTEN 0 128 [::1]:52800 [::]:* users:(("lua5.2",pid=1228702,fd=13))
And it's not the ,
, ;
is ok when multi line.
There are multiple location in my code where i use localhost
. Before changing it, i would like to understand what's happening.
(if i change it, and some people have ipv6 only servers, it could break the plugin for them...)
Can we plan an online meeting, so i can debug it with you? Tomorrow?
Issue was fixed by changing the port in the settings. Prosody had an error log that said that 52800 was already on use for ::1. But we don't understand why. Closing the issue.
Describe the bug
Error messages appear in the logs:
To Reproduce Steps to reproduce the behavior:
Expected behavior No error log
Server (please complete the following information):
Plugin diagnostic:
Additional context
I think you may want to use
127.0.0.1
instead oflocalhost
here