[SUPPORT] SmartPhoneLover - tinyMediaManager


Recommended Posts

  • 1 month later...

So I am trying to use this version of TMM but anytime I try to do anything with it, it just throws errors complaining about not being able to rename/move files. Seems like it does not have write permission?

Yet if I go into the console for the container I can write, move, rename etc into the folders perfectly fine?

Link to comment

How about the Docker or whatever is placing files in your media location? Maybe it has different permissions/user/group set.

 

My umask is also set to 000, which I believe is the default.

 

Mine just updated to 4.3.13 and is working just fine as I just did a set of renaming/moving and meta data adding.

Edited by kricker
Link to comment
5 hours ago, kricker said:

How about the Docker or whatever is placing files in your media location? Maybe it has different permissions/user/group set.

 

My umask is also set to 000, which I believe is the default.

 

Mine just updated to 4.3.13 and is working just fine as I just did a set of renaming/moving and meta data adding.

 

Yeah I considered that as well which is why I tried editing/writing/moving files from the docker console, so inside the TMM instance. It all works fine in there so the docker instance itself is not the issue, it has to be something with TMM it would seem.

 

I also ran the docker safe permissions script from the unraid tools menu as well to make sure permissions were not an issue.

The strange part is it used to work fine, it just stopped working for some reason.

Link to comment
  • 3 weeks later...
On 9/2/2023 at 6:10 AM, Grobalt said:

is this still the correct one ? cannot see it in the community apps and the link to My Repository: https://github.com/SmartPhoneLover/unraid-docker-templates is dead as well

I think this might be a dead project. I have this one installed currently and it works, but I think smartphonelover abandoned maintaining it or something I am not sure

Link to comment
15 hours ago, Indi said:

I think this might be a dead project. I have this one installed currently and it works, but I think smartphonelover abandoned maintaining it or something I am not sure

Yep, their entire github repo was removed so all CA apps were removed as well. I wonder if these topics can all be closed with an announcement since there are similar posts in other threads. 

Link to comment
  • 4 weeks later...
  • 1 month later...
  • 3 weeks later...
8 hours ago, DaveHavok said:

Happy to post up my docker-template that I use with the official TinyMediaManager Docker image if someone needs it.

 

Yes, I still can not get TMM to work on anything, it refuses to write to anything even though I can happily write to the folders from the docker console.

 

It just suddenly broke one day and I can't figure out why.

Link to comment

Docker Template to use the Official TinyMediaManager Docker Image from DockerHub

 

1762839825_CleanShot2023-12-12at10_14_19.thumb.png.f19ceeab18cc6dc111d9ac6c394b7f04.png

 

 

Repository: tinymediamanager/tinymediamanager
Registry URL: https://hub.docker.com/r/tinymediamanager/tinymediamanager
Icon URL: https://i.ibb.co/BVkZTcd/tinymediamanager.png
WebUI: http://[IP]:[PORT:4000]/
USER_ID: 1000
GROUP_ID: 1000
PASSWORD: unRAID

 

728739085_CleanShot2023-12-12at10_21_16.png.6f9d2ad0322146621f0e0004aad1f973.png

 

 

1502187510_CleanShot2023-12-12at10_22_19.png.527177c85905f12928001e4b78457093.png

 

NOTE: Your Host path should point to your media location on your setup

814042315_CleanShot2023-12-12at10_23_54.png.565a15dad05ae8df500a3ec5afb56e79.png

 

NOTE: Your Host path should point to your media location on your setup

 

186668915_CleanShot2023-12-12at10_24_33.png.9d334bbfbddc743ae082be71ed7360c2.png

 

1851923925_CleanShot2023-12-12at10_25_42.png.0112f4a11457c69c76a3932e05598770.png

 

OPTIONAL: 
If you want to use extra parameters with TinyMediaManager and use the launcher-extra.yml file:
Host Path Example: /mnt/cache/appdata/tinymediamanager/extra/launcher-extra.yml

NOTE: I created the extra folder inside of tinymediamanager and within it is my custom launcher-extra.yml file

 

498516328_CleanShot2023-12-12at10_29_31.png.04b81bd23a027e4dbc0ec25fec09c138.png

 

OPTIONAL:
If you want to use custom scrappers you'll need to set this path up between the docker container and your host.

 

NOTE: I created the addons folder inside of tinymediamanager for future use.

Link to comment
  • 1 month later...

Seems like for some reason I can't access the VNC anymore, it used to work flawlessly but all I get now is an error message in noVNC "HTTPS is required for full functionality" and if I click through that I get the prompt for password with the error "New connection has been rejected with reason: Authtentication failure: No password configured for VNC Auth"?

 

I do have the password set in the environment variable

Edited by langelus
adding another error message
Link to comment

Same here,

 

As a workaround, I haver removed the password in the docker (advanced view).

I continue to have "HTTPS is required for full functionality" error. 
But now if I click on Connect in NoVNC webpage, then TMM is displayed like before.

(sorry for my english)

 

image.thumb.png.f887cec1147ba40d4c11464a4c6f1cee.png

Edited by zarkoff
Link to comment

I have been having the connections issues now as well. I have totally started from scratch to experiment. I have found that if I remove the password as stated by @zarkoff it will connect once. If you restart the docker and try to connect again it fails. I then have to re-add the password, start the docker, stop it again, then remove the password, restart the docker then I can connect again. I seem to have to repeat this if the docker ever has to be restarted.

Link to comment

A bit strange, i did not change anything on my system since many weeks and suddenly TMM is not working any more.

 

Logfile:

Fontconfig error: No writable cache directories
2024-01-29 22:02:52,046 INFO success: x11 entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-01-29 22:02:52,046 INFO success: openbox entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-01-29 22:02:52,046 INFO success: websockify entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-01-29 22:02:52,046 INFO success: app entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
Fontconfig error: No writable cache directories
Fontconfig error: No writable cache directories
Fontconfig error: No writable cache directories
Fontconfig error: No writable cache directories

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.