But yeah, I'd have to read up on the basics first.After looking into this a bit and comparing DSM 6.1 to DSM7 I can affirm that the is no longer available with any version below v3, although this is not yet reflected in the minVersion as mentioned above. As long as it's properly mapped to the host IP in the hosts file? And then use that one for letsencrypt.Īpparently there is some nginx/reverse proxy support for synology. So I can basically use any domain I want for the LAN side. It seemed to like that better than putting in the IP for the computer I use. Since I didn't want to use the domain I own I decided just to put a domain name in the hosts file for when I use it locally. In order for Chrome to not freak out you have to generate the cert properly and it actually helped me to add the domain name where they wanted me to. either way, yea I had SSL in place before allowing remote connections.ĭefinitely seems like a bit of longer project it seems :)
It was more of a pain in the ass than I expected but was able to get Let's Encrypt to split the cert and key files so they'd work with SAB and I think Sonarr. Usually this is the directory you've cloned the project to. This needs to be in the directory from which you run docker-compose up -d. env file has to be in the /config as well so the variables get picked up. However, if your containers are correctly set up then they should have nothing inside the container you need to worry about losing - all your config/downloads are likely volumes on the host filesystem.
Unlikely, this will start new containers. It should be possible to adapt this setup to my existing containers somehow. However, if you encounter any gotchas or things of note please do let me know - they can be included in the readme to help others who might come across them. I've not used docker-compose on Synology (assuming you even can). So I'd probably have to manually add the labels If you have any other problems/issues please do post them on GitHub rather than reddit. However, I'll respond directly to your comment here. I usually ask people to post an Issue on GitHub to collect everything in one place to help others. This includes hacking, using a loophole, or other methods not publicly advertised by the usenet provider. No promoting of 'backdoor' access into usenet providers' networks. We do not allow attempts to request/offer/buy/sell/trade/share invites or accounts. We will even add flair to your username after verification. Message the mods and let them know who you are.
However we want to verify the identity of anyone posting on behalf of a company/project.
No discussion of specific media content names, titles, etc. We only have a few, but they are important. Please read over the rules before contributing. We are a thriving community dedicated to helping users old and new understand and use usenet.
0 kommentar(er)
