"Docker safe new permissions" is gone from the Tools menu.

 

I have removed and reinstalled CA Fix Common problems a few times now, and can't get it to reappear.

 

Any ideas?

 

54 minutes ago, tucansam said:

"Docker safe new permissions" is gone from the Tools menu.

 

I have removed and reinstalled CA Fix Common problems a few times now, and can't get it to reappear.

 

Any ideas?

 

No reason what so ever that it should be gone.  Try a reboot?

I am sorry, I am little new here with Unraid. But I lost my Community applications. :

This is error I am getting : 

 

Something really wrong went on during get_categories
Post the ENTIRE contents of this message in the Community Applications Support Thread

No data was returned. It is probable that another browser session has rebooted your server. Reloading this browser tab will probably fix this error

 

I am running Pf-sense as VM and my Version: 6.9.0-beta24, all is stable and works well, but no Community apps. If You have any idea I would really appreciated. 

1 hour ago, Squid said:

No reason what so ever that it should be gone.  Try a reboot?

 

Have done a reboot, yes.  Its gone and won't come back.

 

ETA just tried three different browsers just for kicks, and its gone.

 

Edited October 14, 20206 yr by tucansam

59 minutes ago, emiroslav said:

I am running Pf-sense as VM and my Version: 6.9.0-beta24, all is stable and works well, but no Community apps. If You have any idea I would really appreciated. 

Not related to Fix Common Problems, and ideally belongs in the CA thread, but odds on Pf-Sense is blocking the server from hitting GitHub.com.

 

If you want to help me diagnose why you're seeing that particular message instead of the one you're supposed to see (ie: I can't replicate that message coming up in the same circumstances), see this: https://forums.unraid.net/topic/38582-plug-in-community-applications/page/128/?tab=comments#comment-899908

 

i had multiple problems since few days that forced me to reboot server several times.

Each time the server reboots "Fix Commons Problems" scan the server and throw me errors about share with can only setting setup.

 

I run 6.9 beta30 and i have 2 pools (one for docker the other for vm)

Thanks.  I'll fix in a day or two

I am running 6.8.3 and recently installed Fix Common Problems.  I get an error message that says "Share Music FLAC has read/write set in its included disk settings".  I am not clear on what problem this indicates and how to fix it, if it does need fixing.

Thank you.

8 hours ago, Rudy81 said:

Share Music FLAC has read/write set in its included disk settings"

Can you show me a screen shot of that...

Here you go....

Really strange. "read/write" should be something like "disk1". How did you manage that, that your disk array contains a disk with the name "read/write"?!

 

I think this should be fixed when you select / unselect some of your "included disks" in the share settings for "Music FLAC" and hit the APPLY button.

 

 

3 minutes ago, mgutt said:

Really strange. "read/write" should be something like "disk1". How did you manage that, that your disk array contains a disk with the name "read/write"?!

 

I think this should be fixed when you select / unselect some of your "included disks" in the share settings for "Music FLAC" and hit the APPLY button.

 

 

Well, that worked!  Thank you.  All I did was select all the disks, apply, then deselect and used ALL, apply and Rescan. Presto, no more error message.  Thank you!

3 hours ago, Rudy81 said:

Here you go....

Can you post your diagnostics so that I can see why my tests are failing for you.

I will attach the diagnostics for you here.  Don't know if it will show up, but originally I was working on getting an HBA card to work and was not successful.  The card BIOS would not let the mobo BIOS boot.  Gave up on that for now and began working on moving a bunch of music files to backup. 

tower-diagnostics-20201029-0831.zip

Bug report:

 

If you have any shares assigned to Cache only but you have renamed your default "Cache" pool, fixcommonproblems will trigger the following error. It happens regardless of which cache pool you have that share assigned to and seems to only be checking for "Cache" instead of the applicable cache pool which is assigned.

 

"Share VMsOnCache set to use cache only, but the cache drive is not present"

48 minutes ago, Vaggeto said:

Bug report:

 

If you have any shares assigned to Cache only but you have renamed your default "Cache" pool, fixcommonproblems will trigger the following error. It happens regardless of which cache pool you have that share assigned to and seems to only be checking for "Cache" instead of the applicable cache pool which is assigned.

 

"Share VMsOnCache set to use cache only, but the cache drive is not present"

I know... scheduled fix week of the 8th

10 hours ago, Squid said:

I know... scheduled fix week of the 8th

Haha why am I not surprised! I appreciate all of your valuable work for the community!

 

Is there any other reason why it would be bad to rename from the default "cache" name? I considered not doing out of caution but it made sense now that I had a 2nd cache pool.

Name them as you choose.   Doesnt make any difference to the system 

How can i disable "Syslog mirrored to flash" ? I turned it on a long time ago to track down an issue with freezing-up, but can't remember how i did it.

 

Settings - syslog server  (there should also be a link next to the warning in FCP to take you directly there IIRC)

While testing my beta35 issue with the "close all notifications" button, I saw something with Fix Common Problems. (the extended test generate two notifications, it is quite practical )

 

The extended scan does not find errors (on the page), but the notification of the end of the tests says there is a problem.

 

 Same for the email:

 

Hitting View Results does list some errors though. Few naming stuff and permissions on stuff I don't care so much about. Fixed the former, I'll bother with the later maybe some day.

Anyhow, the No errors / warning found is a bit counter intuitive.

Different tests, hence the notification that shows that extended found something.  But, I do suppose it is somewhat counter intuitive.

I built a template xml for mariadb from scratch (but still using the lsio docker image) and CA Common Problems is flagging it for having the template URL not as the author intended (although I'm technically the author of the template and the template URL is pointing to my personal GitHub account). It wants me to set the template URL to the one for the mariadb in the CA applications store. It even shows up as being installed from the CA applications store, which it was not, it was hand built by me and stored in my personal GitHub repo.

 

I suspect I might run into this again as for some of my other dockers, I'm building custom template xml files for dockerMan because the ones in CA keep enforcing configuration directives I don't want/need and have deleted from the docker containers and it winds up breaking them occasionally when the containers are updated.

 

Which also leads me to a question, I understand that defining and using a repo directly defined in the Docker tab is the older way for custom templates, but I don't see a way in CA to define a custom or private repo. Is something like that possible?

4 minutes ago, amiskell said:

I suspect I might run into this again as for some of my other dockers, I'm building custom template xml files for dockerMan because the ones in CA keep enforcing configuration directives I don't want/need and have deleted from the docker containers and it winds up breaking them occasionally when the containers are updated.

Edit the applicable xml file (/config/plugins/dockerMan/templates-user) and change the line that says 

<TemplateURL>......</TemplateURL>

to be 

<TemplateURL>false</TemplateURL>

and the items which are being re-added to the template during updates won't happen again, and FCP will also no longer complain.

6 minutes ago, amiskell said:

CA to define a custom or private repo

There is.  Toss the templates into /boot/config/plugins/community.applications/private/nameOfRepo/appName.xml  Now any custom templates etc will show up within a category (if they're set), or also within the Private category

 

But, you'd still wind in with the same issue in FCP since it can't determine which you've installed, and assumes that linuxserver/mariadb is the template present in FCP without changing that line above

On 8/19/2020 at 10:02 PM, marlouiegene18 said:

Hello, just installed Jitsi server and i'm getting this warning on CA Fix Problems. I tried to click Apply Fix and gave me an Error: Missing Template. Any thoughts? I tried installing the Jitsi server with encryption but failed so I had to install it without encryption. If that information help. Though if you do know how to install it with working encryption, please let me know as well. I followed Spaceinvader one's video to the tee minus Let's Encrypt as I used Nginx Proxy Manager instead.

 

Thank you in advance for any help!

Bumping this post because I am dealing with the same issue. I have the same four containers with these template missing warnings, pointing to the same A75G templates, for which Apply Fix shows the same error.

I have the following templates on my USB:

$ ls -lhAF /boot/config/plugins/dockerMan/templates/templates/ | grep jitsi
-rw------- 1 root root 4.3K Apr 25  2020 jitsi-jicofo.xml
-rw------- 1 root root 4.0K Apr 25  2020 jitsi-jvb.xml
-rw------- 1 root root  13K Apr 25  2020 jitsi-prosody.xml
-rw------- 1 root root 7.2K Apr 25  2020 jitsi-web.xml
$ ls -lhAF /boot/config/plugins/dockerMan/templates-user/ | grep jitsi
-rw------- 1 root root  4066 Nov 10 10:36 my-jitsi_bridge.xml
-rw------- 1 root root  4336 Nov 10 10:37 my-jitsi_focus.xml
-rw------- 1 root root  7276 Nov 10 10:09 my-jitsi_web.xml
-rw------- 1 root root 12837 Nov 10 10:35 my-jitsi_xmpp.xml

I renamed my containers according to the filenames in the templates-user folder.