404 page not found

[DashingRiggs]

I changed the config to match my local IP and it's giving a 404 error with the status saying the server is offline.

[delcourtfl]

Hello,

This seems strange that you can't access the website as the client seems to be on. Could you share the content of the log files from the 'logs/' folder? I need more information to help you identify the issue.

Additionally, you can try restarting each subprocess by typing their name ('sign', 'client', 'server') in the terminal or reboot the system to ensure that no other process is using the address.

[DashingRiggs]

I just went into the log for the server and it seems to not find ffmpeg. Is there anything to put in the config file to tell your code where ffmpeg is? I already have it installed for another piece of software (https://github.com/yt-dlp/yt-dlp) where I just had to pretty much copy and paste the ffmpeg files into the same folder as yt-dlp.
server.log

[delcourtfl]

To make the server work, you need to make sure that ffmpeg is installed globally on your system and accessible from the command line.

You can check if ffmpeg is callable by opening a terminal and typing: 'ffmpeg'. If the command doesn't work, you have to add the path of the directory containing ffmpeg in your system's PATH environment variable. Alternatively, you can use a Windows package manager like Chocolatey (https://chocolatey.org/), and ffmpeg should become available automatically after the package installation.

[DashingRiggs]

Sorry for the long response, but I still seem to get the 404 not found problem. And yes ffmpeg is now installed, to still have the same issue.

Also, if I just go directly to port 443, it shows like it would normally, besides the fact that it doesn't show the stream

Desktop.2024.02.06.-.23.04.55.12_Sub_01_1.mp4

Here's all my logs if needed.
client.log
server.log
sign.log
video.log
audio.log

[delcourtfl]

Indeed the client page is on port 80 not 3000 (which is used to communicate with the signaling server to establish the WebRTC connection), I might need to clarify this in the README.md.

For the empty stream, it can be caused by many things but most of the time it's an ffmpeg error (you can track it in the video.log), you can try to record other programs to see if it works or play a bit with the arguments of the ffmpeg command in the capture.go file.