@ashman70

Go to post-processing and the episode naming tab and put

Season %S/

before anything else you have in the name patteren. Then you'll get season folders.

 

And just FYI you might want to try medusa instead sickrage, all the sickrage devs except for one went to medusa and are now imo the better fork 

Edited April 15, 20179 yr by strike

If I put it in there as you have it, its says its invalid and I can't save it.

Screenshot?

AH, I think my psychic powers just connected, You probably have one of the standard name patterns, choose custom and make one yourself. 

 

 

Edit: I like using

 %SN Season %S/%RN 

 

Edited April 15, 20179 yr by strike

I am on custom. Here is what I have now and its not saving the episodes in their season folders.

 

Then I have what you are proposing, and as you can see its pink and I can't save it the way it is.

 

 

You didn't add what I said. I said add 

Season %S/

Looks like you're missing "/" If you want Show.Name.Season02 as the season folder name you should add.

%S.N.Season%0S/

Then the rest you want after / And I would personally drop the 0 in %0S or else you will have Season 010 and so on for every season over 9.

I have switched over to using Medusa now, I will post in their support thread.

 

Thanks

Getting an error with sickrage and i cant get sickrage to start

 

11:30:18 INFO::MAIN :: Starting SickRage [master] using '/config/config.ini'
Traceback (most recent call last):
File "/app/sickrage/SickBeard.py", line 545, in <module>
SickRage().start()
File "/app/sickrage/SickBeard.py", line 297, in start
self.web_server = SRWebServer(self.web_options)
File "/app/sickrage/sickbeard/webserveInit.py", line 66, in __init__
if not create_https_certificates(self.https_cert, self.https_key):
File "/app/sickrage/sickbeard/helpers.py", line 863, in create_https_certificates
cacert = createCertificate(careq, (careq, cakey), serial, validity_period, 'sha256')
File "/app/sickrage/lib/certgen.py", line 83, in createCertificate
cert.sign(issuerKey, digest)
File "/usr/lib/python2.7/site-packages/OpenSSL/crypto.py", line 1081, in sign
evp_md = _lib.EVP_get_digestbyname(_byte_string(digest))
TypeError: initializer for ctype 'char *' must be a str or list or tuple, not unicode

 

from here it just keeps repeating over and over in the logs.

 

Any ideas?

 

edit: Of course right after posting i finally find relevant info.

https://github.com/SickRage/SickRage/issues/3795

 

seems to be and issue with htttps and the certs. disabling https through the config.ini has fixed it for the time being. So ignore me.

 

Edited May 30, 20179 yr by Druminstein

On 18.2.2017 at 7:45 PM, Msan said:

I updated to Unraid 6.3.2 yesterday and all seems ok. Today I wanted to log into the Sickrage UI, and I am unable to connect.

Unraid says the Sickrage docker is up and running, I rebooted, reinstalled Sickrage even changed ports.. Still can't get to the webinterface.

This was running fine for months now..

 

Is there anything I can check inside the container? What is the command to start it from inside the container?

 

I have the same problem on 6.3.5.

The log file says:

Quote

INFO::TORNADO :: Starting SickRage on http://0.0.0.0:8083/

The IP address shouldn't really be 0.0.0.0., shouldn't it?

12 minutes ago, whauk said:

The IP address shouldn't really be 0.0.0.0., shouldn't it?

Yes, that means it should answer at port 8083 on any IP assigned to it. That port is inside the docker engine, so that should be the port on the app side of the mapping, you can change the host port to whatever you need it to answer on.

 

What is your docker run command?

Ah, ok, thanks.

I changed it to 8083 - 8081 (standard) is already in use by CP.

Sorry, you had me at run command - I acces it with http://nas:8083/home - but that's probably not what you mean.

7 minutes ago, whauk said:

Ah, ok, thanks.

I changed it to 8083 - 8081 (standard) is already in use by CP.

Sorry, you had me at run command - I acces it with http://nas:8083/home - but that's probably not what you mean.

Where did you change it? I suspect you changed it in the wrong place, causing the issue.

 

Can you post a screenshot of the docker config page showing the ports?

 

 

Edited June 21, 20179 yr by whauk

According to that screenshot, sickrage should be listening internally on 8081 and answering externally on 8083, so when the log for the app itself shows it's listening on 8083 that is wrong, and probably why you can't connect. It should show 0.0.0.0:8081

Oh shoot - I remember, within the Sickrage configuration there was another port mapping field that showed 8081 - which I (pretty much mindlessly) changed to 8083. Guess that's where I made the whole thing break.

I'll give it a try - unfortunately that clearly means to start from scratch as I can't access the inside of the container....

Thanks very much - lesson learned I hope.

 

Edit: Well, in my defense I must say that the explanation line reads " web port to browse and access SickRage (default:8081) "

That can be misunderstood.

But you were right - that was the cause.

Thanks again for saving me an additional couple of days of senseless probing.

Edited June 21, 20179 yr by whauk

29 minutes ago, whauk said:

unfortunately that clearly means to start from scratch as I can't access the inside of the container

Well, you could edit the port mapping in advanced mode and change the app port, or temporarily add a new port mapping pointing to 8083 for the app side.

 

Regardless, count this as your "learned something new" today.

Arggghhh, I didn't see that on this page there is an "Advanced View" button too....[facepalm emoji goes here]

Hi i'm having issues...  I'm new to unraid, but i've successfully in the past few days got Nzbget, Couchpotato and plex running.  I'm slowly porting the services that i have installed on my PC to my Unraid server.

 

Now when I setup Sickrage (i also tried Sickbeard and i get the same issue...), I use the community app to set it up, and when i try to run the webui, it refuses to connect.

Ive attached a screenshot of my current containers and their settings, nothing else is mapped on the same port...  I<ve also attached a screenshot of the settings of the container itself.

 

And this is the command it runs  :

 

Quote

 

root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name="sickrage" --net="bridge" -e TZ="America/Halifax" -e HOST_OS="unRAID" -e "PGID"="100" -e "PUID"="99" -p 8081:8081/tcp -v "/mnt/user/Downloads/Nzbget/completed/TV/":"/downloads":rw -v "/mnt/user/TV/":"/tv":rw -v "/mnt/user/appdata/sickrage":"/config":rw linuxserver/sickrage

fe51fe1dbae11d010448429af52d1c31f9e31be6892b00048e131e549c84ca1f

The command finished successfully!

 

 

 

Any idea ?  Thanks!

PS : this is what shows up in the container's logs :

 

Quote

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 10-adduser: executing...

-------------------------------------
_ _ _
| |___| (_) ___
| / __| | |/ _ \
| \__ \ | | (_) |
|_|___/ |_|\___/
|_|

Brought to you by linuxserver.io
We gratefully accept donations at:
https://www.linuxserver.io/donations/
-------------------------------------
GID/UID
-------------------------------------
User uid: 99
User gid: 100
-------------------------------------

[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 30-install: executing...
Cloning into '/app/sickrage'...
fatal: could not read Username for 'https://github.com': No such device or address
[cont-init.d] 30-install: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
python: can't open file '/app/sickrage/SickBeard.py': [Errno 2] No such file or directory
python: can't open file '/app/sickrage/SickBeard.py': [Errno 2] No such file or directory
python: can't open file '/app/sickrage/SickBeard.py': [Errno 2] No such file or directory
python: can't open file '/app/sickrage/SickBeard.py': [Errno 2] No such file or directory
python: can't open file '/app/sickrage/SickBeard.py': [Errno 2] No such file or directory
python: can't open file '/app/sickrage/SickBeard.py': [Errno 2] No such file or directory
python: can't open file '/app/sickrage/SickBeard.py': [Errno 2] No such file or directory

 

 

Edited July 21, 20178 yr by stefer

Well I figured out that it's no good trying to install containers when your cache drive is full...

 

Cleared some space, and tried again, Sickrage is not responding still, I can run Sickbeard though now that I have plenty of free space (no, not at the same time, i stop one before trying the other one, even uninstall).

 

I'd really prefer to get Sickrage going though...

There is  DMCA in place. See the readme.

1 hour ago, NAS said:

There is  DMCA in place. See the readme.

 

 

yeah the "original" fork of sickrage put DMCA notices on the various forks and on medusa for infringing his copyright.....

 

couldn't make it up....

Yeah I saw that after... was wondering if the containers always use the fresh git data or if they were forked... now i know.

Thanks, i'll stick to sickbeard for some time.

Due to the DMCA now in place on this application, CA has a comment on both the lsio and binhex versions (although Binhex's is still running due to his being a static image).  Hopefully someone will let me know if/when this is resolved one way or another.

Wow, this echol0n is a prick.  Is there a mirror of sickragetv/sickrage anywhere that the docker could point to in the meantime?  

 

Note to self: start mirroring repos I care about...

4 hours ago, dockerPolice said:

Due to the DMCA now in place on this application, CA has a comment on both the lsio and binhex versions (although Binhex's is still running due to his being a static image).  Hopefully someone will let me know if/when this is resolved one way or another.

 

 

for existing users our image is still running, for new users however it won't pull the initial files.

 

in light of this we're beginning to move some of our repos over to having the files pulled at build time rather than runtme, we'd been thinking about it for a while but this situation was the proverbial straw for the camel's back.