On 9/28  I updated unRAID to v6.1.3 since it told me to.  First question:  Are common users expected to apply updates when the GUI notifies one is available or should we be suspicious of updates?

 

Since running that update I've been unable to connect to the MythTV Docker installed using Sparklyballs template.

 

Before the update, I was able to RDP to xxx.xxx.xxx.xxx:3389 as documented in the Mythtv support thread.  Before the update there was a "Port Mapping" entry in the docker container setup.  The install guide recommended not changing the mapping so I did not, it was the default 3389 -> 3389.

 

Since the update RDP has failed to connect on port 3389.  (3387 does still work to connect to Crashplan Desktop - so it's not a universal RDP issue).  Since the update the "Port Mapping" entry is missing from the docker container setup.

 

Mythtv is still working, recording and playing. - I'm trying to get back to the RDP so I can run the MythTV backend setup GUI again to include MythLink.pl as a System Event.

I posted a similar question to the MythTV docker support thread on 9/30. I haven't seen a response to this question yet.

 

thanks

Everend

Try to enable advanced mode when you edit the mythtv docker and add the missing port mapping.

Thanks for the suggestion.  That doesn't seem to be an option.  I am able to change it to Advanced Mode and more options are available, none for the port mapping.

 

The ones that become visible in Advanced Mode are: "Environmental Variables" = blank , "Extra Parameters" = blank , "Additional Fields" = this one has several entries as follows

Docker Hub URL: https://registry.hub.docker.com/u/sparklyballs/sparkly-mythtv/

WebUI: http://[iP]:[PORT:6760]/

Banner: http://i.imgur.com/y2R1EO3.png

Icon: http://i.imgur.com/8co6Sip.png

Description: Myth-Tv installation, SEE SUPPORT THREAD

 

Note that the WebUI has continued to work on port 6760 - same as before the 6.1.3 update.

 

Any RDP issues I have had with the MythTv docker have been solved with a simple docker edit, save (change nothing, it checks for new files, finds none) RDP works again!

IDK if it loses the port mapping or what, but this has fixed it right up for me.

I'd have to look at the template to see if my port mapping is missing, not certain as of now.

 

Try to enable advanced mode when you edit the mythtv docker and add the missing port mapping.

You also have to set it to Bridge mode before it will let you map ports.

SNAP!  I changed it to Bridge mode and a whole list of port mappings showed up.  (previously there was only the one port mapping for 3389->3389).

Well sort of.... I'm work right now so I haven't had time to play with Mythtv since posting that changing it to bridge mode did allow me to RDP into the docker again.  But it just occured to me to check to be sure the backend is actually running and set to record the next show.  MythWeb did load but gave me an error message instead of pulling up the backend status (sorry I didn't write it down).  So I quickly went back do docker and changed it back to HOST. That restored MythWeb to functionality, the error message didn't show when I checked 'backend status'.  I've just set it to record something starting in 2 minutes. lets see if it works.  Oh and RDP does work again.

 

I'll report back later when I'm done with work.