Everything posted by hurricanehrndz
-
TinyMediaManager Container. Accessible through web browser.
The default internal port is 8080 for the web interface and 3389 for rdp. I believe I updated the template yesterday. I will ensure the template is right in a bit. I was using novnc but have no switched to guacamole. Please endure you have updated your templates. Sometimes these means going to the dockers settings page and pressing save on the templates report list. Also the template doesn't map the rdp port so please add it in the configuration page of the container. Please let me know how it works out for you.
-
TinyMediaManager Container. Accessible through web browser.
Wow that's a big bug.
-
TinyMediaManager Container. Accessible through web browser.
Okay. Let me know.
-
TinyMediaManager Container. Accessible through web browser.
I don't think that has anything to do with the container or docker.
-
TinyMediaManager Container. Accessible through web browser.
How did you do that? through exec and the usermapping?
-
TinyMediaManager Container. Accessible through web browser.
That is weird.
-
TinyMediaManager Container. Accessible through web browser.
I see the issue in ms remote desktop client as well, so it must be a settings issue. Can you post an image from experience settings?
-
TinyMediaManager Container. Accessible through web browser.
Yeah, that's because I had vnc cache on. Weird. I will do more testing. The check boxes only appear for me when I minimize and maximize ms remote desktop connector. Did you take that image from guacamole? Or from rdp access? If so which rdp client?
-
TinyMediaManager Container. Accessible through web browser.
So after some testing I noticed checkboxes don't display well. If using an rdp client do you notice much of difference between the last two builds?
-
TinyMediaManager Container. Accessible through web browser.
Awesome. Glad it's working out, this one took a lot of love to produce.
-
TinyMediaManager Container. Accessible through web browser.
Ps you might have to update the template.
-
TinyMediaManager Container. Accessible through web browser.
Okay should be building now, test the web interface now. It runs full rdp communication.
-
TinyMediaManager Container. Accessible through web browser.
Sorry, I will test right now. I made more massive changes to increase performance.
-
TinyMediaManager Container. Accessible through web browser.
Cool! And Thanks.
-
TinyMediaManager Container. Accessible through web browser.
By the way is there a link to your container? I would like to review and contribute if possible?
-
TinyMediaManager Container. Accessible through web browser.
I saw that, you don't want to move away from the phusion image? the only thing I change from forking phusion 0.9.16 was changing the base and nothing else at all. Have we drawn attention to Dev team about compiling the kernel with ipv6 support so that we don't have to do all these work around?
-
TinyMediaManager Container. Accessible through web browser.
Should I take out tinymediamanager and make a base for just the gui part, so that you can fork that and make pull request for additions, and adjustments?
-
TinyMediaManager Container. Accessible through web browser.
Good, let me know if there any additional adjustments you feel are necessary. PS you can make it accessible through a browser using rdp by using the guacamole container.
-
TinyMediaManager Container. Accessible through web browser.
Awesome, happy to hear.
-
TinyMediaManager Container. Accessible through web browser.
Nope by all means, we are here to help each other out.
-
TinyMediaManager Container. Accessible through web browser.
Okay new image is being built on the docker servers as I typed this image. I forked the phusion base image and updated the base os to utopic so that I could an x11vnc binary where I could disable ipv6 from the command line. I tested and so far it works, so please report back. Remember you can now access the container using rdp as well if you map the port 3389.
-
TinyMediaManager Container. Accessible through web browser.
It is by default, the kernel controls everything. If the kernel from unraid doesn't support ipv6 it means we are screwed. Unfortunately the instructions to compiling your own custom kernel for unRAID are a little outdated.
-
TinyMediaManager Container. Accessible through web browser.
Just checked the kerneel config and IPV6 is not set. Wonder if that's the issue.
-
TinyMediaManager Container. Accessible through web browser.
We should really get to the bottom of this because it makes no sense not to have certain images work in unRAID while they work on almost every other issue. Could it be that the kernel in unRAID is not compiled with ipv6?
-
TinyMediaManager Container. Accessible through web browser.
I know, luckily I remember what the issue was. I'm not sure why it only does it in unraid. My ubuntu machine only has ipv4 and the same error doesn't pop up. Maybe it's the way docker is compiled for unraid?