I have just dived in to linux/ubuntu over the last week or so. I've been following guides and tinkering on a clean server, so I had no worries of messing anything up.
I ran a nextcloud app on another server and then followed a guide to make a high peformance server to connect to the talk app.
After nearly a week of following guides, reimaging the server, following guides ,reimaging the server I have finally got to, what i think is the last stage.
I set up the server installing coturn (which was an issue itself because simple 'install coturn' didn't work and I spent a day finding a way to get it installed).
Then installing Janus
Then Nats server
Then nextcloud-spreed-signaling server
and finally nginx and set up a vhost.
After multiple set backs I have finally got to a stage where my turn server set up is working.
However when I try and access the signaling server I get an error in nextcloud.
I have found the source of the issue
When I run:
curl -i https://signaling.domain.co.uk/standalone-signaling/api/v1/welcome
From the hosting server I get the response:
{"nextcloud-spreed-signaling":"Welcome","version":"c8ff009635cb1133a690fe1bdcf5b248c"}
When I go direct to the url I also get the same message.
However when I run the curl command from the server hosting nextcloud the error I get is:
curl: (60) SSL certificate problem: self-signed certificate
I didn't really have to be sherlock to figure out the issue but this seems to be the last hurdle I cannot overcome.
I cannot find a way for me to allow my server to connect to self signed service?