On 3/1/2025 at 2:11 AM, Mainfrezzer said:

what do you get as output when you run 

 

curl -LH "Authorization: Bearer none" https://ghcr.io/v2/ich777/portfolio-performance/manifests/latest | jq .

in the unraid terminal?


If it looks like this


you have to sign out of ghcr.io with 

 

docker logout ghcr.io

The docker token isnt setup to have the read:packages scope, by the looks of it


If it doesnt look like it on the screenshot, something else is going on

Aha, that did it!

Thanks a lot.

Hi all,

I have a problem where I baught a new laptop and installed rustdesk on it.
My environment is unraid with the container
Main pc
vm on the main pc
raspberry pi
vm on unraid

They all have rustdesk, and can connect to each other no problem.
New laptop can connect to the main pc, and the vm on it, but not rustdesk, or the vm on unraid.


When looking at the container logs, i can see successful connections amongst the other machines,and when this machine successfully connects to main or it's vm.

Doesn't seem to generate logs when connecting to other machines, final error on client is
 

Connection error Failed to connect via relay server: Failed to connect to relay server: Please try again later

But server bubble is coming up green down the bottom, and it connects to 2/4 machines just fine.

Firewall are showing everything coming through green (except port 21114 always being blocked, but that seems to be something for the pro version, and container says it doesn't need it)

No idea why this is behaving this way, would really appreciate some guidence, thank you

40 minutes ago, 4554551n said:

Hi all,

I have a problem where I baught a new laptop and installed rustdesk on it.
My environment is unraid with the container
Main pc
vm on the main pc
raspberry pi
vm on unraid

They all have rustdesk, and can connect to each other no problem.
New laptop can connect to the main pc, and the vm on it, but not rustdesk, or the vm on unraid.


When looking at the container logs, i can see successful connections amongst the other machines,and when this machine successfully connects to main or it's vm.

Doesn't seem to generate logs when connecting to other machines, final error on client is
 

Connection error Failed to connect via relay server: Failed to connect to relay server: Please try again later

But server bubble is coming up green down the bottom, and it connects to 2/4 machines just fine.

Firewall are showing everything coming through green (except port 21114 always being blocked, but that seems to be something for the pro version, and container says it doesn't need it)

No idea why this is behaving this way, would really appreciate some guidence, thank you

Correction, when I try to connect, the logs show a new relay request from the target, but not a matching one from the client

 

43 minutes ago, 4554551n said:

No idea why this is behaving this way, would really appreciate some guidence, thank you

I would recommend that you create an issue over here since it's affecting the Server portion from the container:

https://github.com/rustdesk/rustdesk-server/issues

 

Please include more details with screenshots or Code formatted sections from the log (please obfuscated your IP addresses).

For some reason i cannot get my Radarr to load. Even though it has started.. Is there way to download and install a previous or new version. I hopes of saving the current config? I do have a backup but is a few days old..

Or any other advise or help is greatly apprectiated

8 hours ago, roblewis said:

For some reason i cannot get my Radarr to load. Even though it has started.. Is there way to download and install a previous or new version.

Do the following:

1. Stop the container
2. Delete the "logs" folder and every *.tar.gz file you see from the main directory from Radarr which lives usually in your appdata directory
3. Star the container

 

This will reinstall the latest version. I just tried it and the latest version just works fine over here.

Do the following:

Stop the container

Delete the "logs" folder and every *.tar.gz file you see from the main directory from Radarr which lives usually in your appdata directory

Star the container

 

This will reinstall the latest version. I just tried it and the latest version just works fine over here.

 

Will this also fix NZBGet which has broken for me this morning?

error output attached. Was working perfectly up until yesterday and I've not changed anything

46 minutes ago, heppy said:

Will this also fix NZBGet which has broken for me this morning?

Are you using my container? I deprecated it a long time ago since it‘s not actively maintained any more.

 

24 minutes ago, heppy said:

Was working perfectly up until yesterday and I've not changed anything

Are you sure that nothing is blocking access to GitHub or the GitHub API?

 

Do you changed your network gear or do you have any Unifi network gear on your network?

How can i get this giant thread to display STUN/TURN SERVER issues only? I'm trying to get into this, but there is no way to proceed this amount of pages to look for a single issue - is this intended?

2 minutes ago, Gekko said:

How can i get this giant thread to display STUN/TURN SERVER issues only? I'm trying to get into this, but there is no way to proceed this amount of pages to look for a single issue - is this intended?

Sorry, I'm a single developer and creating threads for every container is a bit over the top for me since I maintain about 180 applications.

 

However you could ask what the exact issue is.

 

STUN/TURN Servers usually only work best when they are directly exposed to the Internet without any NAT in front of them, however if your router supports it it could also work when you NAT from your external IP to your internal IP but this is not recommended. That's basically why most of people set up STUN/TURN Servers on Root Server or on a VPS.

On 3/16/2025 at 5:17 AM, ich777 said:

Are you using my container? I deprecated it a long time ago since it‘s not actively maintained any more.

 

Are you sure that nothing is blocking access to GitHub or the GitHub API?

 

Do you changed your network gear or do you have any Unifi network gear on your network?

Curious if poster found a fix. Same thing happened to me and there were no changes to the network. Been stable for a couple of years. 

If I use a new nzbget container, is there a way for me to use the same conf file on it?

1 hour ago, wuckalooka said:

If I use a new nzbget container, is there a way for me to use the same conf file on it?

Sure, just save the current config from the existing container, so to speak the folder in your appdata, install the new container, look at the folder structure and transplant over the config files.

 

Please make sure to stop the new container before copying the files.

14 hours ago, ich777 said:

Sure, just save the current config from the existing container, so to speak the folder in your appdata, install the new container, look at the folder structure and transplant over the config files.

 

Please make sure to stop the new container before copying the files.

 I was able to get the container running by manually specifying the version, but this is good to know. Thank you!

7 minutes ago, wuckalooka said:

 I was able to get the container running by manually specifying the version, but this is good to know. Thank you!

Oh now I know, I removed the versions file from my repository that it pulls the versions from and that's probably why it wasn't working, but as said the application was deprecated I think about one year or even more.

 

I would recommend that you switch over to the new version nzbget-ng I think it is called, but I'm not 100% sure if the configuration files are compatible, hope that helps too.

Thanks for the hint with the version, next time I'll know.

On 3/16/2025 at 4:52 AM, heppy said:

error output attached. Was working perfectly up until yesterday and I've not changed anything

Getting the same error. Noticed it today.

On 3/16/2025 at 5:17 AM, ich777 said:

Are you using my container? I deprecated it a long time ago since it‘s not actively maintained any more.

 

Are you sure that nothing is blocking access to GitHub or the GitHub API?

 

Do you changed your network gear or do you have any Unifi network gear on your network?

Hi @ich777

Started having this issue (noticed it today). I do have Unifi gear on my network (but have for quite a while and no changes have been made).

8 hours ago, wes.crockett said:

Getting the same error. Noticed it today.

nzbget is deprecated by the maintainer and therefore I deprecated the container too, please switch over to another nzbget container.

I suspect something has changed in one of the newer Thunderbird updates?
Since the windows don't have a typical close button I've always used the CRTL + W close tab/window shortcut.
This allows for closing the current window but the keys no longer pass to from the host, just nothing happens.

I've tried using direct IP to container, eliminating Authentik/proxy, it instead closes the host browser window.

You can still type so standard keys are fine.

Since you need to close windows such as mail rules for them to update I can adjust any settings or reduce windows.

Has something changed? Am I doing something wrong?

Edit: I lowered the browser security of the site in Chrome and I have ESC working again 🤷‍♂️

Edited March 22, 20251 yr by ados
Update

15 hours ago, ados said:

I suspect something has changed in one of the newer Thunderbird updates?

I don't think so.

 

15 hours ago, ados said:

Edit: I lowered the browser security of the site in Chrome and I have ESC working again 🤷‍♂️

I assume that something in noVNC or in Chrome changed if you see this behaviour.

I've been trying to reset my data folders according to the instructions in your containers:

Path to your TV Shows bWARNING:/b This style of paths has a performance and disk usage impact: bslow, I/O intensive moves/b and bwasted disk space/b. See https://trash-guides.info/hardlinks/#unraid for details.

 

For example, I've set up Sonarr as follows:

 

Share settings:

 

However, moves after download still seem to be doing a bit-by-bit move, as I can see the filesizes slowly ticking up. I think I've done everything in the guide, any ideas what I'm missing? Run command:

docker run
  -d
  --name='Sonarr'
  --net='bridge'
  --pids-limit 2048
  -e TZ="Europe/London"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="unRAIDpvr"
  -e HOST_CONTAINERNAME="Sonarr"
  -e 'SONARR_REL'='latest'
  -e 'CONNECTED_CONTAINERS'=''
  -e 'UID'='99'
  -e 'GID'='100'
  -e 'UMASK'='0000'
  -e 'MONO_START_PARAMS'='--debug'
  -e 'DATA_PERM'='777'
  -l net.unraid.docker.managed=dockerman
  -l net.unraid.docker.webui='http://[IP]:[PORT:8989]/'
  -l net.unraid.docker.icon='https://raw.githubusercontent.com/ich777/docker-templates/master/ich777/images/sonarr.png'
  -p '8989:8989/tcp'
  -v '/mnt/user/appdata/sonarr':'/sonarr':'rw'
  -v '/mnt/user/data/media/':'/data/media/':'rw'
  -v '/mnt/user/data/downloads/nzbget/':'/data/downloads/':'rw'
  --restart=unless-stopped 'ghcr.io/ich777/sonarr'

1bbbb4fe0e64b514ff97a57ff4ade9c44c6116075089bbd3740c55df817b7412

 

35 minutes ago, Rick Gillyon said:

I've been trying to reset my data folders according to the instructions in your containers:

Please start here:

https://trash-guides.info/

 

You'll find detailed information on how you should set it up here: https://trash-guides.info/File-and-Folder-Structure/

10 minutes ago, ich777 said:

Please start here:

https://trash-guides.info/

 

You'll find detailed information on how you should set it up here: https://trash-guides.info/File-and-Folder-Structure/

Thanks, but that's the guide I already used. I think I've followed it.

6 minutes ago, Rick Gillyon said:

Thanks, but that's the guide I already used. I think I've followed it.

Then everything should work as expected, however if the numbers increase slowly then it might be possible that something is wrong.

 

I assume you've followed this guide: https://trash-guides.info/File-and-Folder-Structure/How-to-set-up/Unraid/

If you did everything should work as intended.

Hi guys, I have installed RustdesktoServer-AiO,

I can find the pub key from the log and use it to connect to remote desktop.

Howerver, my unraid is planned shutdown at night and started on the next day.

I find that the pub key will be changed in RustdesktoServer-AiO logs.

I attach part of the logs as following.

Does anyone know how to solve the issue? thanks.

 

 

[2025-03-29 07:03:16.870134 +08:00] INFO [src/common.rs:147] Private/public key written to id_ed25519/id_ed25519.pub
[2025-03-29 07:03:16.870152 +08:00] INFO [src/rendezvous_server.rs:1205] Key: eslIzrDBYtPdLD4oUPsOi0EeGtvvSlw9V5HEToOK3as=
[2025-03-29 07:03:16.870155 +08:00] INFO [src/peer.rs:84] DB_URL=./db_v2.sqlite3
[2025-03-29 07:03:16.871581 +08:00] INFO [src/rendezvous_server.rs:99] serial=0
[2025-03-29 07:03:16.871589 +08:00] INFO [src/common.rs:45] rendezvous-servers=[]
[2025-03-29 07:03:16.871591 +08:00] INFO [src/rendezvous_server.rs:101] Listening on tcp/udp :21116
[2025-03-29 07:03:16.871594 +08:00] INFO [src/rendezvous_server.rs:102] Listening on tcp :21115, extra port for NAT test
[2025-03-29 07:03:16.871596 +08:00] INFO [src/rendezvous_server.rs:103] Listening on websocket :21118
[2025-03-29 07:03:16.871626 +08:00] INFO [src/rendezvous_server.rs:138] mask: None