Skip to content
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

Connection refused when configured with SSL (self-signed) #40

Open
super23n opened this issue Mar 12, 2020 · 1 comment
Open

Connection refused when configured with SSL (self-signed) #40

super23n opened this issue Mar 12, 2020 · 1 comment

Comments

@super23n
Copy link

Hello,
I have first tried this without SSL/HTTPS and it works good. It seems it should be able to support SSL too, so I am using a self-signed certificate/key files. But now every time I connect with RTMP to publish a stream, I get this in error.log:

[error] 19813#19813: recv() failed (111: Connection refused)

I am not able to connect. I have tried both OBS and ffmpeg to publish. The ffmpeg publish command that I use is:

ffmpeg -re -i "file.mp4" -c copy -f flv "rtmp://192.168.56.53/live/user1?key=KEY-VALUE"

the ffmpeg response is:

Input/output error

Nginx is listening on port 443 and all SSL settings are present. It is strange that connection is being refused by RTMP (port 1935), while SSL is configured for HTTP (port 443).. Do you know what is wrong? Also, I had to add some extra code to the config.php file, namely:

$_SERVER['HTTPS'] = 'off'; or 'on'. Otherwise it was undefined.

@Fenrirthviti
Copy link
Owner

Are you talking about RTMPS? The RTMP portion and the HTTP portion are effectively two different services.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants