Template URL for docker application stuckless-sagetv-server-java8 is missing

[glenner]

Hi All,

Loving my SageTv on unraid! It’s flawless (or pretty close to it :-).

On my unraid server, the “fix common problems” plugin is flagging this error:

“Template URL for docker application stuckless-sagetv-server-java8 is missing”

It has always been this way but never really bothered my until now. I’m not really sure how to resolve this. Has anyone fixed this issue? I need to change my web server port from 8080 to something else (likely 8090) as I have another docker that (really) needs 8080. I think this template issue prevents me from making any changes.

Thanks! -Glenner.

[Striker:WG]

When/where exactly in Unraid are you seeing this warning?

I personally have not seen this come up and I am running the Java 8 docker container that you are referencing.

[glenner]

Sure. There is an unraid plugin called "Fix Common Problems". I have always had it installed as it seemed to be recommended by many experts and is provided by Squid (unraid senior expert).

https://forums.unraid.net/topic/4726...mmon-problems/

This thing runs monthly in my case, and sends me an email of basic issues with my unraid instance I may want to fix.

Once you install the plugin, you will see an icon for it under "settings". You can then run a scan, or schedule a scan, and it will report on configuration issues.

In my case, it reports this:

Template URL for docker application stuckless-sagetv-server-java8 is missing.

It then actually proposes this fix:

The template URL the author specified is https://raw.githubusercontent.com/st...rver-java8.xml. The template can be updated automatically with the correct URL.

And there is a button to "Apply Fix". I will try this now, and see if this fixes the issue.

[glenner]

I ran the “apply fix” and it seems to have corrected whatever was wrong with my docker template. I then updated the web port from 8080 to 8082 in the docker config. I also updated the jetty plugin web server port config to 8082 and the SageTV webui now runs on port 8082.

Unifi controller software running on unraid seems to really want port 8080, and I could not find a way to change it.

[KeithAbbott]

I just got a similar message from the "Fix Common Problems" plugin, except for the crazifuzzy-opendct docker. I clicked the "Apply Fix" button, which appeared to resolve the issue. Here's the screenshot after the fix was applied:

[jusjoken]

Interesting. The copy of this template on OpenSageTV is part of the work I am doing to get the docker templates cleaned up, current and supportable by myself and the community.

I will post more info on this work I am doing but it was a surprise to see the fix common problems found the relationship and it worked for you... glad to see.

K

[KeithAbbott]

Originally Posted by jusjoken

Interesting. The copy of this template on OpenSageTV is part of the work I am doing to get the docker templates cleaned up, current and supportable by myself and the community.

I will post more info on this work I am doing but it was a surprise to see the fix common problems found the relationship and it worked for you... glad to see.

K

So now that I have a different template than the crazifuzzy-opendct docker was originally created with, are there any advantages or disadvantages to my new situation? I'm asking this question not only for myself, but any others that may run into the same situation that are running that docker.

[jusjoken]

Originally Posted by KeithAbbott

So now that I have a different template than the crazifuzzy-opendct docker was originally created with, are there any advantages or disadvantages to my new situation? I'm asking this question not only for myself, but any others that may run into the same situation that are running that docker.

At this time that docker has not changed as I have not reviewed it.. Just hosted it. I will review this docker in time and see how we can have options in the docker templates to support opendct including potentially optionally embedding it if that makes sense.

K

[wayner]

Originally Posted by jusjoken

At this time that docker has not changed as I have not reviewed it.. Just hosted it. I will review this docker in time and see how we can have options in the docker templates to support opendct including potentially optionally embedding it if that makes sense.

That probably makes a lot of sense!

[technazz]

Originally Posted by jusjoken

At this time that docker has not changed as I have not reviewed it.. Just hosted it. I will review this docker in time and see how we can have options in the docker templates to support opendct including potentially optionally embedding it if that makes sense.

K

+1 Please