can you provide a log? I want to see why the 3rd 5th 7th logins failed
Sent in PM: Hopefully it is enough of the log. The system kept telling me it was too long to send.
You can dump a portion of the docker log. This --since=24h will output the last 24hrs into the file
/volume1/arkives/frndlycontainer.log
sudo docker logs -t --since=24h frndlytv-for-channels >/volume1/arkives/frndlycontainer.log 2>&1
I setup a task that runs as root hourly to update the file, so I don't have to log into my Synology to see the log.
docker logs -t --since=1h frndlytv-for-channels >>/volume1/arkives/frndlycontainer.log 2>&1
Works great. Very much appreciate the time spent creating and maintaining. My first custom channel, btw. I did the python method and it took me a while to figure out I had to download and install Git in addition to Python. I am noticing that in the server window a keep alive is recorded every 5 minutes. Is this being sent to Frndly? Thought I read above it should be every five hours? Next question: Does Channels pull multiple streams at a time with this or is the subscription stream limit enforced by the Frndly servers? If this does allow us to pull more streams that we pay for, would option to limit streams in the Channels server source management handle that task?
It logs in every 5 hours. It checks if the token is still good every five minutes (“keep alive” is slightly poor terminology) and will force a login if the token has for some reason expired.
The “keep alive” is really mainly for people who may have issues with their sessions timing out due to login delays. Up until recently login was done on demand as necessary. The new process is to simply stay logged in all the time and not allow the token to expire. This can be turned off by using KEEP_ALIVE=0.
My personal hunch is that the original on-demand behavior is good for most people and would recommend using KEEP_ALIVE=0 unless you encounter problems with recordings or timing out while changing channels. But I’m not the developer, just a fan. Lol.
Ok… I just recorded 5 different channels off Frndly at the same time while watching 2 live streams on an iPhone and AppleTV. So I would say the Frndly steam limit doesn’t apply.
Yes, if you enter a limit and exceed it you will get the a nice Channels logo screen with the message “stream limit reached”.
Correct, and the resolution is not hamstrung down to SD.
The Frndly app works great. We are getting a better viewing experience than folks that just use the app.
Thanks for all the hard work.
1 Like
This might be a noob question but I have hit a roadblock. I run channels on a Synology nas. I set up the docker program on the synology nas as well. When I try to create the custom channel I get this message, " invalid source url: Get "http://192.168.11.224:49156/playlist.m3u8": dial tcp 192.168.11.224:49156: connect: connection refused." As far as I can tell there are no security limitations set up. I run the command to start it with the username and password with no special characters in the password to get it going. " docker run -d --restart unless-stopped --env "USERNAME=**" --env "PASSWORD=" --name frndlytv-for-channels -p 8183:80 matthuisman/frndlytv-for-channels" . The log file says at the end of it, "Exception: USERNAME and PASSWORD are required." Is there somewhere else I am supposed to put the username and password? I would be glad to send the logfile to someone. I don't have the option to attach it here. I am sure I am missing something obvious. Thanks
For the custom channel setup you should use this for the playlist
http://192.168.11.224:8183/playlist.m3u8
Assuming your Synology running the frndlyTV docker is at IP address 192.168.11.224
If you view the web page of the frndlyTV docker is should have the link to copy. Here's mine
Playlist URL: http://192.168.1.3:8183/playlist.m3u8
Also your docker run command needs to have your frndlyTV username and password filled out.
--env "USERNAME=yourusername" --env "PASSWORD=yourpassword"
Unfortunately I am still getting a connection refused message. Is there somewhere else I am supposed to be putting the username and password other than that command line script? Thanks, Mike
No. Maybe it has special characters in the password?
Is the docker container running?
What do you see at http://192.168.11.224:8183
You can also view the container details from the Synology web UI
Docker > Container > Details
This will show the Environment Varialbles, so you can see what USERNAME and PASSWORD it got from the run command.
The container is running. There are no special characters in the password. Here is what I am getting: See screenshot.
1 Like
What do you see at the container page http://192.168.11.224:8183
And did it get the correct username and password?
You can also view the container details from the Synology web UI
Docker > Container > Details
This will show the Environment Varialbles, so you can see what USERNAME and PASSWORD it got from the run command.
It doesn't seem to like port 8183. When it does show me what the playlist link is supposed to be it takes me to http://192.168.11.224:49163/. But it stops working after I try to run the command to feed the credentials. The credentials are correct.
To use the run command again you have to stop and delete the running container first.
Make sure you stop and delete all frndlytv-for-channels containers that are running, then do the run command again.
And to make sure you are using the latest version also delete the frndlytv-for-channels docker image before doing the run command again.
I deleted all the containers and redownloaded it from the repository.
I only have one instance running. This is what the log looks like:
I don't have a status page the local address using port 8183 or port 49156 where it was before. This is what I am running in the command line: "docker run -d --restart unless-stopped --env "USERNAME=-------------------" --env "PASSWORD=---------" --name frndlytv-for-channels -p 8183:80 matthuisman/frndlytv-for-channels"
No dice. I am stumped.
I appreciate your assistance to help me trouble shoot this so far. I don't know what else I can tell you to help me figure this out.
Sounds like you are running it twice.
The commandline docker run command will download the image, create the container and run it.
If you also did something in the Synology Docker app, you are duplicating things.
Stop and delete the container.
Delete the image.
Now Don't use the Synology Docker package to do anything this time.
Issue the docker run command.
Once it downloads and runs, then look at the Synology Docker app just to see what port it's running on.
1 Like
And I assume you know the basics.
To issue the docker run command you need to establish an SSH session to the Synology using something like putty.
The docker run command must be run as the root user.
So either sudo docker run ...
Or sudo - to establish a session as root.
Make sure to pay attention to any error messages you might get when doing the docker run command.
1 Like
I believe I did as you asked. I deleted everything out of the docker app, image and the container.
I then ssh'ed into the Synolgy nas and got this response:
And it looks like that works and solved all of the issues for the most part.
But the quide isn't quite there. I guess that will fill in as it downloads.
1 Like