killeriq

No clue what is wrong, but either after some OS reboot or new Transmission update it puts the default value as when you installed fresh Transmission docker and it put the "ip white list" rule ON again, even i removed it in docker and in settings.json drives me nuts when i find out after some time that again i cant log in

upgrade to RC3, and what a surprise again all Transmission settings resetted to default @linuxserver.io could you please fix the docker? Thanks

check lower / upcase letters , needs to be correct in mappings / folders. Had similar issue

had the same problem, fixed! thanks

Dead?

And again...seems like each automatic docker "update" , it get messed up @linuxserver.io Could someone fix it once and for all? Thanks

dont copy, just edit few values... it behaves strange and it happend to me even i removed those "white" values in docker, after restart it was there again. 2nd wipe fix it, then is compare and edited settings.json, no overwrite overwrite cause that not wanted values were there again

1. check / save your docker settings 1.1 backup appdata/transmission (otherwise *.torrent will be lost) 2. remove docker and appdata/transmission 3. install it again 4. remove those "whitelist" fields from docker setup 5. compare old settings.json with new settings.json and modify as needed No clue what they messed up, acting strange

what did u set as "peerport" in config?

i'm aware of that, from some reason even "stopped" changed json and after start old values again... I removed app from docker, deleted transmission in appdata, installed again and now it seems its fine...lets see if it last. Drives me nuts already

after few days, same problem again It added those values again...

I was facing the issue with RPC "without password" seem like it was in this state multiple months. Until i found out and removed the former docker, installed latest one. Now seems like new issue, even i setup "settings.json" it get changed after restart and im not able to use Transmission I even removed those values from Config in Docker, but seems like they show up again Any clue what else to change to "keep/save" settings i setup? Thanks EDIT: I overwrite again the "settings.json", stopped Docker and started - all seems saved now Also tried restart - settings are kept. Maybe is some docker "update" in between causing it, will see till next update. for now FIXED

Solution: 1. Wiped the whole docker as finded out that "DB" file is not part of backup before upgrade. 2. Install it from scratch 3. Setup MariaDB instead SQLite with was needed to add (https://techoverflow.net/2021/08/17/how-to-fix-nextcloud-4047-innodb-refuses-to-write-tables-with-row_formatcompressed-or-key_block_size/) 4. Then "rescan" of all files and putting them all to newDB via OCC command https://mangolassi.it/topic/21018/nextcloud-scan-local-files-into-db Very helpful as it didnt went to download / upload from scratch Then i wanted to try finally SWAG (internet access to Nextcloud) followed those guides: https://knilixun.wordpress.com/nextcloud/ https://medium.com/@chrismorris_82249/setup-a-reverse-proxy-nextcloud-server-on-unraid-using-letsencrypt-831905d94f7d , also done but i would like to set it up via ports and no clue how. If someone could assist , would be great

Hello, I'm looking for an suggestion how to setup SWAG / Nextcloud that it would use also port behind domain... All is working fine, port fwd etc. 1. When i enter url (internet - out of my LAN) : mydomain.duckdns.org It goes directly to my Nextcloud Login page. What i want to archive to type URL with port mydomain.duckdns.org:8888 and then get the Nextcloud login page. As i might want to use it for multiple dockers and not creating / changing it for each Docker (as spaceinvader does) In example: Nexcloud - "mydomain.duckdns.org:8888 " Grafana - "mydomain.duckdns.org:8889 " Plex- "mydomain.duckdns.org:8890 " Is this possible? if so what i need to change in config? ## Version 2021/05/18 # make sure that your dns has a cname set for nextcloud # assuming this container is called "swag", edit your nextcloud container's config # located at /config/www/nextcloud/config/config.php and add the following lines before the ");": # 'trusted_proxies' => ['swag'], # 'overwrite.cli.url' => 'https://nextcloud.your-domain.com/', # 'overwritehost' => 'nextcloud.your-domain.com', # 'overwriteprotocol' => 'https', # # Also don't forget to add your domain name to the trusted domains array. It should look somewhat like this: # array ( # 0 => '192.168.0.1:444', # This line may look different on your setup, don't modify it. # 1 => 'nextcloud.your-domain.com', # ), server { listen 443 ssl; listen [::]:443 ssl; server_name mydomain.*; include /config/nginx/ssl.conf; client_max_body_size 0; location / { include /config/nginx/proxy.conf; include /config/nginx/resolver.conf; set $upstream_app nextcloud; set $upstream_port 443; set $upstream_proto https; proxy_pass $upstream_proto://$upstream_app:$upstream_port; proxy_max_temp_file_size 2048m; } } 2. After i setup SWAG and i want to open Nextcloud locally via WebUI, it redirects to "mydomain.duckdns.org" and not able to open it. Only way it works when i enter Nextcloud Docker IP manually: 192.168.1.123:8989 How to get it working "oldway" ? thanks

Repair error: An exception occurred while executing a query: SQLSTATE[HY000]: General error: 11 database disk image is malformed Please any clue where is the DB file i need to fix / replace? I'm using default SQLite i guess, probably due to Cache disk issue i get this error and cannot start Nextcloud now. I have some backups which are automatically created (before update), so i assume i should be able to fix it somehow. So i wiped "\appdata\nextcloud\www\nextcloud\*.*" and copied whole backup, but message still presist... Where / What else to check? thanks

I was getting, but command wasnt working, so i removed NodeRed Docker. removed folder in Appdata and after installed it again, but now it doesnt want to even start and giving me this error:

I just realized that my DB is getting error " influxdb lvl=info msg=Unauthorized log_id=0S_B9NMW000 error="token required" " thought what is messed up again, seems like it was in this state for few weeks and not updating DB at all... I found the suggestion to change the docker to 1.X instead of "latest" Here are also all versions listed seems like https://hub.docker.com/_/influxdb/?tab=tags&page=1&ordering=last_updated So currently im on "influxdb:1.8.4-alpine" version and it works! Thanks! 1. What the alpine means? (some Beta/Alpha release? ) 2. If i want to move to "latest" again "2.X" what should i go? I see this post the telegraf part iI should be able to do, but i dont understand the "Grafana" part what is "InfluxDB OSS 2.0" do i want "Flux" or "InfluxQL" ? 3. Does the "old" data 1.X from telegraf will be kept also in 2.x+ version? Thanks

nope , in the end i sort it our without Weewx

you are using H.264 to show in Browser? i havent compared the delay by second, but when i try via "Guarding Vision" app on Win is much more smoother then via Shinobi, seems like is not the best option for Cams

Thanks for tip i wil try... General question is : How can today app "Shinobi" be that behind with support of new codecs? Or if we say browser - those are most updated apps on internet i would say Firefox, Chrome etc. should have support for that The WebUI for those chinese cameras video live view, have some plugin to install , but it works only on IE or IE Tab extension within other browser.

Guys did anyone been able to run live stream in H.265 / 265+ codec? Soon as i turn H.265 on Camera (Web UI setting) it stop to work (just black screen). Soon as i turn it back to H.264 it works again. I thought that H.265 its already wide used (lower data consumption), but if Shinobi is not really able to use it, then its not very usable as of today. @SpaceInvaderOne in Video p.3 you mention that you had issues with H.265 so you are using the H.264. Just to confirm issue was with Shinobi same as i have? Not with the camera it self? On NVR device or NVR via Web or Guarding Vision works everything fine...even on the iSpy i was able to get picture/video, not on Shinobi which is sad Thanks

Hello, Today ive tried CrushFTP9 from you. Initial setup went fine, but got popup from CrushFTP Update to 9.3.2 and then it stopped to work... So in App update is not wanted and need to wait for docker update? Thanks

thanks for info ! finally Btw here is some workaround which i find useful in my case

Also requesting patch if possible @limetech - Could you please apply this fix ? many users with 3xxx Ryzen are having this issue, would really appreciate it to release quick fix for that. Thanks!

Hello, I would like to Request for IOBroker docker template, as im not able to get it working :( https://hub.docker.com/r/buanet/iobroker/ https://forums.unraid.net/topic/61663-need-help-with-iobroker/?tab=comments#comment-863899 Thanks!