Froberg

Mine's up at http://x.x.x.x:9091/transmission/web/ I did not modify it from the default afaik.

So the container, for me, is broken right now. Web interface never loads, log indicates this: To support LSIO projects visit: https://www.linuxserver.io/donate/ ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- [cont-init.d] 10-adduser: exited 0. [cont-init.d] 30-config: executing... [cont-init.d] 30-config: exited 0. [cont-init.d] 99-custom-files: executing... [custom-init] no custom files found exiting... [cont-init.d] 99-custom-files: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done. 2020-05-27 18:16:24 INFO MAIN :: [918cfe7] Broken providers found: [''] 2020-05-27 18:16:27 INFO MAIN :: [918cfe7] 12345: Unable to find the show in the database 2020-05-27 18:16:28 INFO MAIN :: [918cfe7] 353095: Unable to find IMDb info in the database: Torben Chris Rydder Op 2020-05-27 18:16:28 INFO MAIN :: [918cfe7] 380840: Unable to find IMDb info in the database: Savmordet 2020-05-27 18:16:28 INFO MAIN :: [918cfe7] Starting Medusa [master] using '/config/config.ini' 2020-05-27 18:16:28 INFO TORNADO :: [918cfe7] Starting Medusa on http://0.0.0.0:8081/ 2020-05-27 18:16:28 INFO MAIN :: [918cfe7] Updating exception_cache and exception_season_cache 2020-05-27 18:16:28 INFO MAIN :: [918cfe7] Finished processing 3250 scene exceptions. 2020-05-27 18:16:28 INFO MAIN :: [918cfe7] Building internal name cache for all shows It's tempting to blame the 0.0.0.0 address, but it seems like the UI *is* up on the proper address. It just does.. nothing.. except display a loading animation. I tried forcing an update to no avail. Any suggestions? I'd rather not lose my database after all. Update; further inspection, and obvious troubleshooting, resulted in FireFox being to blame in this instance. All is well in Chrome. Huh.

Yeah me too. My piHole is in br0 and has an IP address assigned, and I can access it just fine. NPM just can't, to my knowledge, access the other virtual networks for the remapping. Anyone feel free to correct me, of course.

It has been a while since I set it up, but I think it only functions correctly when used in bridge, otherwise it can't access what it needs. I went through the same issue, I'm pretty sure, actually. Point being; I'm fairly sure it that it needs to be in bridge mode for it to be able to reach the addresses of other systems in bridge mode. Not sure if creating an entirely separate network for nginx and web-facing services would work though.

Why do you want to? You have app.plex.tv for managing it. Failing that, just launch web-interface from the plex docker.

Yes, well, the intent of the docker is to expose it to the internet to some degree, makes sense to me that it's password protected by default. If you haven't actually made any setup, just remove it and re-install. If it persists with the data during this, you can always use Community Application Cleanup App Data to get a fresh start - or just specify a different app-data directory (config directory) during initial setup of the docker. The config directory if you wanna poke around in console is @ /mnt/user/appdata/NginxProxyManager per default, I couldn't find anything to manually define a local user at a cursory glance.

I want something with fairly low power consumption, since it'll be running 24/7. I don't see intel delivering on that any time soon, sadly. And Plex can't utilize AMD as yet, unless I missed the news or something.

William is, indeed, one awesome individual. I have an ASRock Rack Board myself and have also been in contact with him. Extremely perceptive, helpful and I can't imagine what ASRock Rack would be like without him. Personally I'm not sure what to upgrade with. I want to use my current board (C2750D4I) as my backup box, but I am completely stumped on what to replace it with. I really don't want such a demanding CPU, as I don't really have the need for it. I would like to be able to throw up a VM though, so yeah. Guess I just have to keep an eye on ASRock Rack releases.

You're saying that it works outside your network? I had a similar issue with a Linksys router, that had a feature that I of course can't remember what was, that specifically prevented something like nginx working from inside the network. Outside it was fine. Maybe look at your router settings and try turning some stuff off?

It should be in bridge. As should Sonarr, by the way, AFAIK. I have medusa and transmission in bridge mode and all is well in the world.

There's a community application "cleanup appadata" that can ensure you get everything.

Seems your settings are identical to mine. It's probably down to the vpn-specific stuff, then. I'd try removing the docker entirely and re-adding it all other things being equal to what worked for you before. I'm assuming you're sure that your PIA is paid and active of course.

What are your network settings for the docker?

No guarantee either US or UK supports port forwarding. I have success with Israel.

Select another country and try again.

Side note; you had a setting; add_header Strict-Transport-Security "max-age=15768000; includeSubDomains; preload;"; Does that help with the issue of nextcloud timing out during update procedures?

Anyone else experiencing the docker memory leaking itself to death after the latest update? It's suddenly starting at 700ish MB memory and then just growing until it reaches my max-limit. I've just had to change it from a 2GB to 4GB limit just to mitigate a bit. Anyone else noticed this? Update; well it's been a week without killing itself, here's hoping - and a new update came out too. It's running at a stable-ish 1GB memory use.

Depends on router upnp, either way it's ports opened by my reckoning. Edit; opening up to the possibility that I am wrong on this, so if anyone knows better, feel free to correct me. Mine's just running on the local LAN - but since it's BT protocol one assumes that upnp be required. But yeah.

1. You can select the ports, but yes, you need to be able to open ports. Using VPN would void this requirement, although I've not tried setting up a specific docker over a VPN other than one that came with VPN built-in. 2. Log issue is solved by setting log-values for the docker. 3. No. Less overhead on a docker, but it's a web-ui so.. I just realized I could've been more helpful regarding the log-issue; I've set this as extra parameters on the docker; --memory=2G --log-opt max-size=50m --log-opt max-file=1

You have to share the mapped sync folder over the network if you want to access it via file explorer and give your user permissions to the share. You have to map the sync folder as a user share. Or just add stuff to your client and let it sync.

Usually you mean to sync from somewhere, to somewhere else. Not necessarily two-way. If you want to sync from a device to your NAS, for example, you should select the stuff you want to sync on your device and get a read key. Then enter that key on your NAS GUI and it will start syncing everything in that folder on the device. The same goes the other way around. This is a filesharing or sync application, not a dropbox type thing. If you require that, go for something like NextCloud or OwnCloud.

That's interesting - and good to know, too, as I might need to use that myself eventually. Thanks for sharing. I was going to get back to you, but I've been swamped at work.

Just add however many volume mappings you want and specify the specific folders? The default set-up is intended, I believe, for simple 1:1 sync between two folders on two devices, using it to sync multiple locations is outside of normal usage, but should work fine regardless. Adding the specific volume mappings should make them visible in the UI just fine though.

That did it. Documentation for those that want it: Permissions are now persistent. That's awesome. Kind of want to suggest this become a part of the main image, but hey, at least there's an option to get it workin'. Now to see if the watch directory will function. Thanks man, made my life a whole lot easier.

Yes I figured as much, it doesn't change how the docker behaves when starting up though. It still sets restrictive permissions on the entire transmission directory. I haven't been able to figure out what is responsible for that.