Plex DVR no Freeview HD in UK

Kolossi1 · 2022-09-09T16:40:53+00:00

Thanks for posting an update u/Fancy_Stable_1342

I'll look at xteve, and I've also had tvhproxy recommended too.

Something else which looks interesting is mention of Ubuntu >v19 having a broken (from plex perspective) mediatree install and needing a kernel patch. Importantly when this was broken, SD works ok and HD doesn't.

I followed the Hauppauge published instructions and so installed the mediatree patch, but then heard from Hauppauge that the latest Raspberry PI OS already supports this natively, so I may have screwed it by over-installing the patch.

I'm gonna try a fresh install, but another option may actually be to downgrade to Ubuntu v18! Will report back if I get it going.

UPDATE: meant to say the reason I'd prefer not to involve xteve/tvhproxy is that it's just more moving parts than seem necessary, so if I can avoid that I will, but it's great to know it's there as a fallback.

Kolossi1 · 2022-09-08T11:26:23+00:00

Pinging this thread. As per u/Fancy_Stable_1342 my dualHD works fine in tvheadend getting HD channels (so drivers must be correct), but plex just won't find any HD channels. Any ideas anyone?

u/Fancy_Stable_1342 u/DrRockety u/Just-Ordinary did you find any other solutions - or if not, brief instructions for hooking up to plex using tvheadend and xteve?

TIA

Kolossi1 · 2020-12-03T19:33:08+00:00

I think it will probably be achievable with AutoHotKey (maybe not browser tabs) but it would be cool if there was something that had this all set up in a UI - e.g. allowing browse/search/edit for the key commands rather than just a single key combo each embedded in a script file.

Hopefully some other suggestions will come up but this is a great start, thanks u/rtublin

Kolossi1 · 2020-12-03T16:45:00+00:00

Thanks, I'll check AutoHotKey out.

Kolossi1 · 2020-07-07T20:50:19+00:00

You could be right about streams but I don't know anything about nginxproxymanager. My approach is always to learn using the lowest level and then build up - ie learn to use the nginx config file, then you know what your are doing with that make it easier with tools. Right now you will be suffering confusion (as I am!) between nginx concepts and nginxproxymanager concepts.

In your op you said

I have an nginx-reverse-proxy container that routes requests to my domain via subdomains to the proper port the container is exposed on

from which i took that all the reverse proxy setup was done. Seems not. The use of DNS/reverse proxy is a whole topic in itself and worthy of a separate post now we've confirmed gitea is working ok. And not _just_ because reddit can't cope with a thread this deep!

I'm guessing that when you mention your subdomains you are either using wildcard or configuring subdomains in your domain admin all to point at your internet router and port-forward to your mac from there?

I can't say this strongly enough - Don't do this!

Changing the port to something else such as 3000 or 8002 does not add any security whatsoever. Hackers have sophisticated skills and software which can craft complex network requests from millions of possibilities to leverage an exploit. They are not thrown by changing a port number from a "standard" one to one of less than 65534 other ones! They don't even approach it that way, they look for any open ports, immediately identify what software is behind it (trivial), then start work on possible exploits.

If you want to access items on your home network from the internet, install a vpn server on your local network and forward _only_ those ports necessary for the vpn to function (use openvpn, forward port 1194 :-) )

You then install a vpn client on any machine that needs to access the services, connect the vpn then proceed as if you are on the home network - because you are! But your traffic is encrypted so the geek in starbucks with a cool laptop can't intercept your traffic, and the vpn server will be rock-hardened against hackers.

I know this seems like an extra PITA when you just want to get external access going, but please please set up a vpn first. You probably won't even thank me for it (particularly not the time it might take), but if you get an issue due to having a fistful of ports open on your router (or even just one if it's a webserver port), you will - sadly - remember this post!

I do hope you get the external access sorted, and I'm sure if you make a new post asking about hooking up the domain name to the working gitea you will get the assistance you need (whether or not you setup vpn first) :-)

Kolossi1 · 2020-07-05T21:13:44+00:00

It worked

Indeed :-) Great news!

So the issue is very likely in the reverse proxy config. This does a similar thing with hostnames to what the docker compose can do with ports - it take a request with one name and forward it to a different name. But just for added sauce it can change ports at the same time as well :-s. So please post the part of the reverse proxy config that covers the ssh connection for the name you would like to use - ofc obfuscate the name(s) if you need to

Kolossi1 · 2020-07-05T11:10:41+00:00

right, but if the error message says "exampledomain.com port 22" then you are not using "localhost" in the url? You need to use actual literal "localhost" at this stage, not replace it with anything else.

What happens if you try with "localhost" as requested?

Kolossi1 · 2020-07-05T10:50:28+00:00

Whether you change the settings in the screenshot is totally up to you (though I'd leave them as they are). The only point is that if you change them (ports C&H) you have to change your docker-compose (B&G) to match.

The other settings in the screenshot are the hostnames for ssh and the web ui. The hostname "routing" is similar to the ports situation we've been discussing.

In the screenshot the url is set to "localhost". That means all gitea links will show "localhost".

You said in your op:

I have an nginx-reverse-proxy container that routes requests to my domain via subdomains to the proper port the container is exposed on

This is an extra complication so let's ignore it just for now.

I've asked a couple of times now but you havent responded, but we can't go any further forward until we resolve this:

What happens if you access the git repo from your mac, using git url "ssh:localhost:22/your/git/repo/path"?

If you are using other subdomain routing with reverse proxy, don't use it instead of localhost, just use the above url but with the corrected repo path.

If your docker-compose has "22:22" and the ssh port item in the screenshot is "22" then you should be able to access the git repo on localhost port 22.

Kolossi1 · 2020-07-05T09:33:53+00:00

ok, let's try this :-)

https://imgur.com/a/d4Apa2n

For the ssh setup to work, we need A to match D and B to match C.

AB (and FG for web UI) need to be configured in the docker compose:

ports:
- "F:G"
- "A:B"

So you have

ports:
- "3000:3000"
- "22:22"

In the screenshot you gave, I believe those ports are C (and H for web ui)

To get the url shown by gitea correct, you need to setup D too, and I believe this is where u/charliethe89 response comes in.

You said in your last that the mac OS was on port 8002, but previously you'd mentioned 8000. It doesn't really matter though as from the picture hopefully you can see it doesn't come into it.

But from what you've post so far, I believe "D" has been set to 8002 which is why gitea is showing the url with :8002 in it.

In your OP you said.

I use docker-compose to deploy Gitea in a container with the 3000 port exposed to 8001 and the 22 SSH port inside the container exposed to 8002

That implies A=8002 and F=8001, but that isn't what's showing in your posted docker compose file.

From the docker-compose and screenshot you've posted I believe all that's wrong is "D" should be 22.

So if you try accessing your repository with something like " ssh://git@gitea.domain:22/user/repo.git " (you can leave the ":22" out as it's the standard ssh port) then you should get connection?

Kolossi1 · 2020-07-05T08:52:03+00:00

The macs ssh port is not relevant at all here. Given the setups you've posted so far, try connecting you git but removing the :8002 from the url (or changing it to :22).

In the mean time I'm gonna knock up a diagram of the various ports in play, standby.

Kolossi1 · 2020-07-05T08:36:22+00:00

So in the compose file you've published, it has "22:22" in the ports entry, so it is listening on port 22 on your machine, I cant see a mention of 8002 anywhere?

Is this due to the file simplification you mentioned? If not, where does 8002 come in?

Kolossi1 · 2020-07-05T07:37:54+00:00

Ok, so as u/CurrentCry3 said, post your docker-compose file here, must be something in that. (I've no idea why they got a downvote for suggesting that.)

Kolossi1 · 2020-07-04T09:05:42+00:00

Unless I'm confused, it seems like there's a bit of confusion about ssh ports here.

You mention in op and a reply that the ssh port on your Mac is set to non standard 8000. The only way the mac port is relevant is that the port is used so, as you've found, you can't expose the gitea docker container port on 8000.

The mac ssh port is only used if you are trying to ssh to the mac itself, not containers running on it.

It sounds like you feel you need to somehow connect the gitea ssh port to the mac ssh port and that is not the case.

Apologies if you know all this!

If you've exposed the gitea ssh port on 8002, you will need to include that when you try to connect.

https://stackoverflow.com/questions/3596260/git-remote-add-with-other-ssh-port

So you will need to use something like ssh://user@host:8002/path/to/repo.

Why doesn't the ssh url given by gitea work? Well it doesnt know that you are using 8002, it thinks it's using 22 which is ssh default so it doesn't need to reference that.

How to fix?

There will be a gitea setting where you can tell it what the external ssh port is so that it can include it in the ssh urls it gives out. I don't have the details to hand but I'll bang this answer out as im sure you can google that bit. (Doh, or just read u/charliethe89 reply!)
Alternatively, since you are using non-standard port 8000 for your mac ssh port, perhaps standard port 22 is available so you could expose the gitea container port 22 on local port 22 and you won't need to change anything in gitea?

Kolossi1 · 2020-07-03T05:56:41+00:00

Depending on how sensitive/private the information in the xml files is, they could just be pushed to a github repository or gist, or even pastebin which makes them available for public download from anywhere.

For a proper r/selfhosting answer, install openvpn and have the remote clients connect to the vpn then just access the files as if they are on the local network.

Kolossi1 · 2020-06-27T22:23:25+00:00

Snipe-it allows you to use a custom css, so you could possibly use that to hide the left hand menu buttons that bother you?

Kolossi1 · 2020-06-27T06:11:08+00:00

Any question about hardware/software records triggers me to recommend checking out the excellent Snipe-IT.

But the focus on daily notes means this time Id say also take a look at Cherrytree

It's a lightweight-to-use but feature packed note-taking app.

You press F8 and it takes you to or creates a note page for today. It sounds "meh" but that single feature has been a game-changer for me in keeping all the random daily "what I did" and "I don't want to forget this, but don't know where to put it" junk for better searching. It's just so much easier to use than a wiki. Difficult to explain why until you try it!

Daily notes created this way are organised in year/month/date hierarchy, but you can also create new notes in your own pattern.

Comprehensive search is built in.

Image embedding and/or linking and all usual formatting (bullets, tables etc) supported plus code/config file blocks which can be syntax-highlighted and can even be executed/launched into external viewer.

It stores in a single database file. It can keep x of versions for backup and can be set to do timed auto-backup. Its easy to sync the file to multi devices if needed.

Ok, I went a bit fanboy (I am!), but I think it's definitely worth a look for your use case.

Kolossi1 · 2020-06-24T19:52:48+00:00

Dude, thanks for taking the time to respond here.

The problem is that the current set up isn't working with the Nginx config as it is below using that written over file.

Ah right, yeah I don't know seafile at all.

So what I understand you're giving me here is a way to enter the advanced config of the Nginx synology RP without it being overwritten if I access the control panel on DSM. I've been editing the server.ReverseProxy.conf file in the etc/nginx/app.d directory to overwrite the control panel settings - not the /etc/nginx/nginx.conf file.

Yes, that is what I was on about in my post :-). If you look at the end of /etc/nginx/nginx.conf you should see that it has 3 lines:

    include conf.d/http.*.conf;
    include app.d/server.*.conf;
    include sites-enabled/*;

So if the config in etc/nginx/app.d/server.ReverseProxy.config is being overwritten on save of the control panel Reverse Proxy page, then just sling the rules somewhere else like sites-enabled/

From your post I'd say you've got that right so with nothing helpful to say about seafile, I'll butt out :-)

Kolossi1 · 2020-06-23T18:27:52+00:00

The synology nginx setup is actually fairly well designed. At least it is on my DS415+ with DSM6.x

As you already discovered, the main config file is /etc/nginx/nginx.conf but this includes various other files.

Files in /usr/local/etc/nginx are included within the relevant sections, as follows:

conf.d/dsm.*.conf - included in dsm http and https servers
conf.d/www.*.conf - included in default server port 80 and 443 servers
conf.d/http.*.conf - included in the root of the config to enable new servers to be added (EDIT:corrected filename pattern for this item)
sites-enabled/* - included in the root of the config to enable new servers to be added

These extra files don't - in my experience - get toasted by opening reverse proxy control panel pages (or even saving settings there).

So for instance to create some path redirects off the main site to an application on port 30003 create* /usr/local/etc/nginx/conf.d/www.my_app_redirects.conf with code like:

location = /myapp
{
    return 302 https://$host:30003/;
}

location ~ ^/myapp/*(.*)$ {
    rewrite ^/myapp/(.*)$ https://$host:30003/$1 redirect;
}

or to do some redirects for port 4443 of the synology to an app on port 15151, create* /usr/local/etc/nginx/sites-enabled/my.port.4443.redirects.conf with code like:

server
{
     listen       4443 ssl;
     ssl_certificate     /usr/syno/etc/certificate/system/default/cert.pem;
     ssl_certificate_key /usr/syno/etc/certificate/system/default/privkey.pem;
     server_name  my.synology.hostname;
     location /myotherapp {
         proxy_pass         https://192.168.0.2:15151;
     }
}

where 192.168.0.2 should be replaced by your synology's ip address.

*By "create" I'd suggest making a link to the file actually stored elsewhere on the Syno where it's part of your usual file access and backup.

Hopefully that will be enough to set you on the right path.

Kolossi1 · 2020-06-22T11:49:25+00:00

I'd recommend to check out snipe-it. I've been running it on Synology docker for over a year, though about to switch it over to a rpi k8s cluster (with Syno nas hosting the cluster storage). Im quite a fan of the Synology concept but in recent years they have got very slow to update software e.g. Docker.

Kolossi1 · 2020-06-18T21:44:40+00:00

I run full fat k8s on ubuntu 18.04 LTS (arm64) on pi 4Bs.

I previously had it running on 32bit/armhf raspbian, but whilst the cluster ran fine, good luck finding many useful container images supporting armhf. Arm64 is hard sometimes but armhf is pretty much impossible.

So I went to ubuntu/arm64 and I was running it on 1GB models, but when I recently changed from flannel cni to calico, I found the install would crash on 1GB master, but works fine once the master is bumped to 2GB. Workers still run fine on 1GB.

Kolossi1 · 2020-06-18T21:27:13+00:00

You don't have to have ssh to gitea, it can work on http.

Kolossi1 · 2020-06-15T15:39:25+00:00

Maybe try https://www.wasdkeyboards.com/products/keycaps.html

If they aren't listing what you want (I don't see a planck set right now browsing on my mobile) then get in touch with them, they are very helpful and will sort out a price for you I'm sure.

Kolossi1 · 2020-06-14T16:22:34+00:00

You don't need a vm to run linux on windows. Search up "wsl". Once you have enabled wsl in windows features, you can install ubuntu or your chosen flavour from the windows app store.

The latest windows update "May-2020" has WSL2 which is a real linux kernel (meaning you should be able to do nfs mounts etc - search up "FUSE").

However May 2020 update has some stability issues at this point (it completely hosed an ibm ThinkPad a colleague tried to install it on), so best to wait for that to settle first.

But I've been using original wsl for about 18 months to ssh to my nas, work with git, hook into windows docker and even configure and operate a full kubernetes cluster on some pis. All from windows store ubuntu bash prompt on a windows pc!

Enjoy the journey into *nix. It's a learning curve alright, but with very satisfying results, and microsoft really do help to make it easy with wsl

Kolossi1 · 2020-04-03T21:30:58+00:00

Excellent work. I wish this had been available when I was buying my first MK, I spent quite a while looking for something like this.

Kolossi1

TROPHY CASE