Nostr Web Client

Do you have the web server available via the internet?

What it should be doing is streaming to the www/live folder. You should see an output file and a bunch of ts files there. Those are the files that need to be accessible via internet. The nostr event uses the external url config for the url on the nostr event. So it should be accessible via yourdomain.com/live/output.m3u8

DeAllen Young 4mo ago

https://live.deallenyoung.xyz

Reply to this note

Please Login to reply.

Discussion

OceanSlim 4mo ago

Hm. Should be showing then. Not sure. I'll hop on desktop in a bit and see if theres anything in the console on your site for clues. Do you have stuff in the archive folder now? Because if so, it should be showing in the vault.

DeAllen Young 4mo ago

Nothing in archive. I have it set to live-only

OceanSlim 4mo ago

When you're live, do you see the output files in live

DeAllen Young 4mo ago

Nope, but from restreamer I can see that it's connected. From gnostream server I can see the IP of viewers. The 1935 and 8080 are up. That's about it. I've tried changing the host IP for rtmp from quad0, 127, localhost and the IP issued from DNS. I made a systemd service file, to running it in the background. I added rtmp support, added it to nginx.conf. I wasn't sure if I needed to do that.

OceanSlim 4mo ago

Do you have ffmpeg?

OceanSlim 4mo ago

The rmtp server does not have to be available to public. Because you are just streaming to it locally and the program makes hls files to serve on the webpage as a stream.

DeAllen Young 4mo ago

I fixed it! There was a conflict with ffmpeg. Upgraded to Trixie and all is right as rain. 🫡⚡

OceanSlim 4mo ago

I'm home now. Tag me when you try again and I'll check it out!