PaulieORF
-
Posts
20 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by PaulieORF
-
-
I've got the plugin installed with a backup schedule set for my Home Assistant VM, and it works perfectly. I even tested doing a restore (in case the day comes where I'll actually need it) and it worked as expected. My only nagging problem is every time my scheduled backup runs, I get the following notification from Unraid:
Event: Unraid Status Subject: VM Backup plugin Description: cannot run /boot/config/plugins/vmbackup/configs/home-assistant/ Importance: warning 2022-01-14 03:00 User script file does not exist. Exiting.I never put anything in the pre or post-script locations in the config for this backup because I don't have any scripts I need to run. Is it normal for the plugin to report a warning if you do not have a script set to run as part of your backup? Is there a way to stop this notification?
Note: When I run the backup manually, it does not trigger this notification.
Thanks
-
6 hours ago, ionred said:
@ljm42 I think it had to do with this being a reinstall. I can't recall the status of my backup before but it's possibly related.
I just fixed it for myself. I did the following steps to get it working:
*wiped the /boot/.git directory
*removed /var/local/emhttp/flashbackup.ini
* then manually initialized with php /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup.php activate
Perhaps more checks are needed on a reinstall to remove the .git directory and any leftovers from a previous install to prevent this?
Edit: the last step may have been unnecessary to manually activate from the CLI. I did not refresh the myservers page in the GUI to see if it would work automatically. I can say for sure that just removing the .git folder under boot was not enough, though.
Just followed this and it worked for me. Flash backup is not functioning! Woohoo! Thanks.
-
I installed and setup the My Servers plugin in April and all was good. I hadn't thought about it for a while, so I opened up the plug-in and saw that the flash backup (which originally was working fine) was now showing "fatal: .git/index: index file smaller than expected", as you can see in the screenshot I'm including. I have rebooted my server, signed out and back into My Servers, uninstall and re-installed the plug-in, and so on. All the while My Servers shows that it's online. I've also not been able to find any posts on the community or internet in general regarding this error. I'm hoping someone here is able to help, as a regular flash backup would definitely help me sleep easier at night! Thanks in advance.
P.S. I'm running 6.9.2.
-
On Transmission_VPN, I've switched to using NordVPN instead of PIA. I've got Nord working using the provider specific variables. Part of getting Nord to work for me was deleting the OPENVPN_CONFIG variable. However if I restart the docker container, OPENVPN_CONFIG is automatically created again and points to a PIA config, causing the docker to not start properly because it can't connect. If I manually remove the variable again and then restart the container it works, but the OPENVPN_CONFIG variable will always come back on subsequent restarts. How can I make it so OPENVPN_CONFIG does not keep coming back?
Thanks
-
Everything has been smooth with this container forever. Suddenly when I attempt to access the web UI, I am prompted for an email address and password. I've never seen this before, and I can't seem to get past it. Any help would be greatly appreciated.
EDIT: I tried the default email address and password with no luck. I ended up just trashing the container and files, and just starting over again. Back up and running now.
-
8 minutes ago, clowrym said:
can you switch to advanced view and send again....
Should look similar to this:
Looking at your run command there is somthing wrong with your second one as your getting '1198:admin/udp' rather then '1198:1198/udp'
Oh okay. I had to enable advanced view to see all the fields. For the VPN_PORT value, it was listed as "admin" for the container port but it was grayed out, so I was unable to edit it. So what I did was delete this port and create a new one for it. Set the container port to 1198, set it to bridged, and now it's rocking and rolling as it should. Thanks for your help!
-
4 minutes ago, clowrym said:
Can you click edit on your port entries and show me whats inside, there is something wrong. Mine looks like this:
-p '9091:9091/tcp' -p '1198:1198/udp'Where your's look like this:
Sure thing. Here ya go.
-
2 minutes ago, clowrym said:
Switch netowrk type to bridge.
When I switch to bride, I get this. And then the docker container becomes an orphaned image.
-
3 hours ago, clowrym said:
Thats an odd issue, I have always had mine set to the Host IP & only Transmission traffic is routed through my VPN. can you post your settings for the container?
Sure thing. See attachment. Thanks!
-
Regarding haugene/transmission-openvpn...
I've been using this container for years on its own IP address with no issues. I've decided I want to run it using the host's IP. The container works, however the entire Unraid host and any other docker containers that also run using the host's IP are now having all their internet traffic routed through the account I've got the Transmission_OpenVPN container connecting to. There's got to be some way to make it so the VPN connection is isolated to just this container, right?
Thanks in advance.
-
16 minutes ago, Froberg said:
I have not seen that message. I've attached my https setup for reference.
Is yours set up similarly?
I've figured it out. I had to turn HSTS on in my Cloudflare account. All good now!
-
2 hours ago, Froberg said:
As I set this up a few months ago I might actually be of use here.
Assuming you set up the proxy-part correctly, maybe you're missing some steps in the owncloud config. (i.e. forcing https, maybe..)
Check your config.pgp and ensure the following lines are present:
'overwrite.cli.url' => 'your.domain.goes.here', 'overwritehost' => 'your.domain.goes.here', 'overwriteprotocol' => 'https',(substitute your own domain, of course.)
You also need to make sure that the Nginx Proxy Manager and the NextCloud container is on the same ip address.Have you been able to over come this message?
QuoteThe "Strict-Transport-Security" HTTP header is not set to at least "15552000" seconds.
I've got HSTS turned on in Nginx, but this still shows up.
-
2 hours ago, Froberg said:
As I set this up a few months ago I might actually be of use here.
Assuming you set up the proxy-part correctly, maybe you're missing some steps in the owncloud config. (i.e. forcing https, maybe..)
Check your config.pgp and ensure the following lines are present:
'overwrite.cli.url' => 'your.domain.goes.here', 'overwritehost' => 'your.domain.goes.here', 'overwriteprotocol' => 'https',(substitute your own domain, of course.)
You also need to make sure that the Nginx Proxy Manager and the NextCloud container is on the same ip address.Wow, so my problem was that I had the Nextcloud container using its own IP address. Just changed it to the same as the Unraid server and it's now working. Thanks!!
-
Has anyone been successful in getting Nextcloud working through the Nginx Proxy Manager docker? I've been able to get other dockers and a VM to work through it, but not Nextcloud. I can't find a guide, and solid info on getting the two working together seems pretty sparse.
Thanks
-
On 12/21/2018 at 1:14 PM, Djoss said:
@amacdonald, currently, Nginx Proxy Manager doesn't have the support for forwarding to a HTTPs backend/server.
In the meantime, if you really want to have your nexcloud forwarding working, you can manually edit the generated Nginx config to make your proxy works:
In /mnt/user/appdata/NginxProxyManager/nginx/proxy_host/, find the file associated to nextcloud. You then need replace the directive "include conf.d/include/proxy.conf" with:
add_header X-Served-By $host; proxy_set_header Host $host; proxy_set_header X-Forwarded-Scheme $scheme; proxy_set_header X-Forwarded-Proto $scheme; proxy_set_header X-Forwarded-For $remote_addr; proxy_pass https://$server:$port;
Finally, restart the container.
Note: if you do a change from the UI, the config file will be overwritten and you will loose your changes!
It's been quite a few months since this workaround. I do see in the Nginx Proxy Manage now that forwarding to HTTPS servers is supported, however I still cannot get it to work with my Nextcloud container. I get 502 Bad Gateway. Is there some other trick in getting this working? Thanks!
-
Thanks!
I actually just got finished formatting the cache drive, restoring the data (using the community plugin) and then re-adding my docker containers. So far, everything seems to be working great and the appdata share is working as expected.
-
Thanks for the quick response.
"Use cache disk" is set to "yes" under Settings > Global Share Settings > Cache Settings.
I'm attaching my diagnostic zip.
-
This is my first post to the forum. I've been using Unraid for six months now without any issues, but yesterday I encountered my first and it's pretty weird to me.
In my setup I have a 500 GB SSD as my cache drive, and have my appdata share set to "prefer" the cache drive. I browsed to my appdata share through Windows, as I wanted to look at something in my Plex logs. Strangely the share shows as empty. No files, no folders. If I go through the "cache" share directly, the appdata folder is there with all its contents. This explains why my dockers were all running fine. Inside the Unraid web UI, if I go to the shares tab and click on the folder next to the appdata share, it shows that it's empty there too.
I randomly decided to browse back to the appdata share through Windows and try to create a new folder. I received an error from Windows saying the folder was no longer located there, or something close to that. However if I go into the cache/appdata folder, I can see the "new folder" that it created. If I go back and try to create another folder, I get the error once again, but do see the "new folder(01)", "new folder(02)", etc.
I'm left scratching my head on this one. I dug around on the forums, Reddit, and Google in general and can't find anyone documenting this same behavior.
Your help is greatly appreciated!
[support] digiblur's Docker Template Repository
in Docker Containers
Posted
Is everyone else still stuck on this? I've deleted the container and image and reinstalled, but as soon as I check for docker updates I get back to "not available".