Python 3.7.7 issue with sickrage

Since upgrading see the below problem after doing some troubleshooting to see if it a TVDB issue or other issue.

hope this info helps

#1. Python version.
3.7.7-12
sickrage 9.4.221-18
SABnzbd 3.0.1-42
#2. Operating system.
Synology DS918+ 6.2.3-25426 Update 2

#3. sickrage.log file.
Warning after restore of backup
2020-08-23 08:04:22 SEARCH-PROVIDERS::Invalid token error, please re-link your SiCKRAGE account from settings->general->advanced->sickrage api
2020-08-23 08:04:22 SEARCH-PROVIDERS::Invalid token error, please re-link your SiCKRAGE account from settings->general->advanced->sickrage api
2020-08-23 08:04:22 SEARCH-PROVIDERS::Invalid token error, please re-link your SiCKRAGE account from settings->general->advanced->sickrage api
2020-08-23 08:04:21 SEARCH-PROVIDERS::Invalid token error, please re-link your SiCKRAGE account from settings->general->advanced->sickrage api
2020-08-23 08:04:21 SEARCH-PROVIDERS::Invalid token error, please re-link your SiCKRAGE account from settings->general->advanced->sickrage api
2020-08-23 08:04:21 SEARCH-PROVIDERS::Invalid token error, please re-link your SiCKRAGE account from settings->general->advanced->sickrage api
2020-08-23 08:04:21 SEARCH-PROVIDERS::Invalid token error, please re-link your SiCKRAGE account from settings->general->advanced->sickrage api
2020-08-23 08:04:20 SEARCH-PROVIDERS::Invalid token error, please re-link your SiCKRAGE account from settings->general->advanced->sickrage api
2020-08-23 08:04:20 SEARCH-PROVIDERS::Invalid token error, please re-link your SiCKRAGE account from settings->general->advanced->sickrage api
2020-08-23 08:04:20 SEARCH-PROVIDERS::Invalid token error, please re-link your SiCKRAGE account from settings->general->advanced->sickrage api
2020-08-23 08:04:20 SEARCH-PROVIDERS::Invalid token error, please re-link your SiCKRAGE account from settings->general->advanced->sickrage api
2020-08-23 08:04:19 SEARCH-PROVIDERS::Invalid token error, please re-link your SiCKRAGE account from settings->general->advanced->sickrage api
2020-08-23 08:04:19 SEARCH-PROVIDERS::Invalid token error, please re-link your SiCKRAGE account from settings->general->advanced->sickrage api
2020-08-23 08:04:19 SEARCH-PROVIDERS::Invalid token error, please re-link your SiCKRAGE account from settings->general->advanced->sickrage api
2020-08-23 08:04:18 SEARCH-PROVIDERS::Invalid token error, please re-link your SiCKRAGE account from settings->general->advanced->sickrage api
2020-08-23 08:04:18 SEARCH-PROVIDERS::Invalid token error, please re-link your SiCKRAGE account from settings->general->advanced->sickrage api
2020-08-23 08:04:18 SEARCH-PROVIDERS::Invalid token error, please re-link your SiCKRAGE account from settings->general->advanced->sickrage api
2020-08-23 08:04:17 SEARCH-PROVIDERS::Invalid token error, please re-link your SiCKRAGE account from settings->general->advanced->sickrage api
2020-08-23 08:04:17 SEARCH-PROVIDERS::Invalid token error, please re-link your SiCKRAGE account from settings->general->advanced->sickrage api
2020-08-23 08:04:17 SEARCH-PROVIDERS::Invalid token error, please re-link your SiCKRAGE account from settings->general->advanced->sickrage api
2020-08-23 08:04:16 SEARCH-PROVIDERS::Invalid token error, please re-link your SiCKRAGE account from settings->general->advanced->sickrage api
2020-08-23 08:04:16 SEARCH-PROVIDERS::Invalid token error, please re-link your SiCKRAGE account from settings->general->advanced->sickrage api
2020-08-23 08:04:16 SEARCH-PROVIDERS::Invalid token error, please re-link your SiCKRAGE account from settings->general->advanced->sickrage api
2020-08-23 08:04:15 TZUPDATER::Updating network timezones failed.
2020-08-23 08:04:15 ANNOUNCEMENTS::Invalid token error, please re-link your SiCKRAGE account from settings->general->advanced->sickrage api
2020-08-23 08:04:15 SEARCH-PROVIDERS::Invalid token error, please re-link your SiCKRAGE account from settings->general->advanced->sickrage api
fixed advanced->sickrage ap by clicking branch and verify git path popup stated already on branks
Still seeing timezones failed. no difference if I select local or network
double checked router ipv6 is off and NAS has it disabled on interface connected to local network
issue 1
unable to add new show or update existing shows I get timeout to TVDB

issue 2
unable to connect to SABnzbd local on the same server
Nothing loged on sab logs to indicat anything tried to connect and if I point to a PC on local network with WireShark installed I see no frame from NAS for the SAB port looks like the underlining script not working in sickbeard or is blocked
access SAB web interface from the PC to nas with no issue so seem like internal issue between apps. Both Sab and Sick have group accesss to sc-downdoad and sc-media

I also see
Error getting caps xml for [NZBGeek]
Maybe this caused by the timezone issue

I’ll take a look at this later today.

OK, I tested adding “The Blacklist” and had no problems doing so, please confirm if this issue is still present, will now test and see if I can reproduce the SAB issue.

As you can see in the image below I was able to connect SR to SAB


No go for me hmmm something is hosed.
I keep checking.

Thanaks
Dan

What happens when you try it without the API key ?
Is you’re SAB the latest version ?

Same issue if I remove key and on sab screen does not show any indication any fail to connect.
3.0.1 [9a4be70] I believe latest I see on package Center

Do you do the Docker builds also?
I see that it seem to wok and connect to sabnzb and tvdb and was able to manual add show again?
used same Sab install just installed docker and created a sickrage container.
thanks
Dan

Yes, i do the docker builds as well

Maybe the app it self was blocked by synology firewall ?

Yea looked at that but firewall disabled.

I am going do more test today as I found if I uninstall remove sickrage then install sickbeard custom it connect to sab

What difference it install old phython 2
Docker version does not use 3.7.7

Docker version does use Python 3
https://hub.docker.com/repository/docker/sickrage/sickrage

hmm it show 3.8.5 in this screen?

yes Docker image is built on Python 3.8