Jump to content

CorneliousJD

Members
  • Posts

    692
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by CorneliousJD

  1. New UniFi Video docker - set to Bridge mode - which I would realllllly like to keep it at, but unfortuantely it's having issues now with adopting a new G3 Micro - this is my first UniFi video cam and it wont adopt into the NVR unless I have the container on its own IP w/ br0 mode set. This means it cannot talk to my other containers in bridge mode now though because of this, which means I can't use the cameras in the way I was hoping. Any way to get it working again in bridge mode as it was templated? Thanks!
  2. AppDaemon is an execution environment for writing automation apps for Home Assistant home automation software. It also provides a configurable dashboard (HADashboard) suitable for wall mounted tablets. For full instructions on installation and use check out the AppDaemon Project Documentation. I did not create Appdaemon or HADashboard, I simply created the template for unRAID because I wanted to share Appdaemon and HADashboard with the unRAID community. This docker container REQUIRES Home Assistant as well. A docker container for Home Assistant already exists, just search "HomeAssistant" in the apps tab! The variables you need to set when setting up this container for the first time are as follows. HA_URL: This is the URL to your Home Assistant installation. Example: http://192.168.1.100:8123 Make sure you do NOT add a trailing / at the end, this will break AppDaemon and prevent it from connecting to HomeAssistant. TOKEN: This is a LLAT (Long Lived Access Token) from HomeAssistant. DASH_URL: This is a hidden paramater and can be left alone, you can change it if you know what you're doing though. Note that the first time you launch this container it will fail and exit. This is because it created an example appdaemon.yaml in /mnt/user/appdata/appdaemon/ Go ahead and edit that file (I use nano via the terminal to do so personally) and add a few lines that are required. In particular for the current release you need to add time_zone, latitutde, longitude, and elevation in order to get Appdaemon to actually run in the container without crashing. Here's a base example config, please change to suit your own timezone, latitude, longitude, and elevation. Note that your HA_URL, Token, and Dash URL will automatically all be filled in. appdaemon: time_zone: America/Detroit latitude: 0 longitude: 0 elevation: 0 plugins: HASS: type: hass ha_url: http://X.X.X.X:8123 token: REMOVED FOR SECURITY http: url: http://$HOSTNAME:5050 admin: api: hadashboard:
  3. Awesome, thanks for confirming! The container works great and I'm loving it, makes backups so easy and have successfully restored after losing my entire cache drive too. Couldn't be happier with it!
  4. I am getting a warning about 75% of max memory being used. Only actively backing up ~500GB of data with this. Just to note I installed this container fresh and setup all new backups for this server, I did not migrate from anything else. This is the first time I've seen this error since setting it up about 4 months ago.
  5. Looks like OpenVPN-as in Host mode was causing some overlap which made discovery not work at all... Turning off OpenVPN-as and then booting this container up seems to let it run fine. I should probably change OpenVPN to use br0 mode instead of host mode I guess.
  6. I'm having some trouble with this container also. I want to use the letsencrypt container to do a reverse proxy on this so I can access from outside, however the issue I'm running into is whether in bridge or host mode, HomeAssistant can never see any of my devices, and can only be seen if I put it into br0 mode and give it its own IP address. I have tried privilege on/off in bridge/host most but it cannot auto-discover my devices still. Is there a way to get this to work without assigning it a separate IP? Once I do that I lose access to allow my letsencrypt container to do a reverse proxy, unless I go back and reconfigure a bunch of containers... Oof.
  7. I was able to sort this out by following the guide a bit more closely for the specific file that they make - i had originally tried adding it to default site-conf, but after I copied the existing nextcloud config they had up in the tutorial all is well.
  8. I've gotten everything up and running but am seeing the following 3 errors in the admin section on nextcloud. The "X-XSS-Protection" HTTP header is not set to "1; mode=block". This is a potential security or privacy risk, as it is recommended to adjust this setting accordingly. The "X-Content-Type-Options" HTTP header is not set to "nosniff". This is a potential security or privacy risk, as it is recommended to adjust this setting accordingly. The "X-Robots-Tag" HTTP header is not set to "none". This is a potential security or privacy risk, as it is recommended to adjust this setting accordingly. Do I need to make changes in the nextcloud site config or the letsencrypt site config? I am reverse-proxying via letsencrypt container. Thanks!
  9. Thanks so much for this - I tweaked their setup every so slightly but it's working great for me now! Uploading my existing data into nextcloud now. Excellent! Thanks!
  10. I'm with you! I know we're staying off the pihole container support here but willing to help provide logs/sepcs/etc from my build that's not having any issues if needed anywhere, feel free to PM me if ever needed to drop more logs into something. I have a 4U supermicro w/ 4x onboard gigabit NIC ports.
  11. Thanks, I don't have much data to bring INTO next cloud really, since Plex allows access to all my media I'm not worried about media files, so it's all just documents/photos for one user (just me) and I can import those in fairly easily I think. What did you do in MariaDB for setting up NextCloud, did you just use your root user/pass?
  12. Hi all, I posted over in the MariaDB forum but haven't heard anything back just yet. I want to make sure I'm doing this correctly. New MariaDB install that i want to use for Nextcloud for now, and possibly more in the future. I have HeidiSQL on my Windows box that I can manage the DBs with. I was going to create a separate user that is NOT root as I understand this is the right way to do things? e.g. create a "nextcloud" user and a "nextcloud" database. My question is what privileges does that user need and how do I grant them just to that one database? Thanks. PS - Right now my /data is just going to /mnt/user/nextcloud which is a share I have setup for nextcloud data - is this the correct way to do this? I'm under the impression I shouldn't point it at a share that I already have existing with documents/pictures/etc in it?
  13. That's super weird. I have a Supermicro server and haven't had any call traces like that so that's really odd, sorry you're having such trouble. Hopefully more people report it if/when it occurs so that it can get the attention it needs then. In the meantime I would suggest setting up a quick debain VM, if you're not familiar with the linux terminal you can install a GUI and still run pihole with a few simple commands on the terminal. The GUI will help you with things like setting a static IP for the VM, etc. This is what I was doing up until I decided to give the docker container another go and got that working so I killed off my VM.
  14. This is also how I used to run it. I just had a debian VM setup with command line only and no GUI for being as lightweight as possible. It worked well, but I've since migrated to the docker container and I run it with its own IP... sounds like you have some deeper issue if running a container with its own IP is causing call traces. Post diagnostics and logs in the general support forums maybe? If you can get that sorted out then this docker container should work for you.
  15. Hi All, I want to make sure I'm doing this correctly. New MariaDB install that i want to use for Nextcloud for now, and possibly more in the future. I have HeidiSQL on my Windows box that I can manage the DBs with. I was going to create a separate user that is NOT root as I understand this is the right way to do things? e.g. create a "nextcloud" user and a "nextcloud" database. My question is what privileges does that user need and how do I grant them just to that one database? Thanks.
  16. According to this https://github.com/diginc/docker-pi-hole/releases you SHOULD be able to edit the container to have this as the repository diginc/pi-hole:v3.3 I'm not 100% sure that will work, basing this off of my Ombi container that is linuxserver/ombi:65 from here: https://github.com/linuxserver/docker-ombi/releases As I'm running the version listed as tag 65 due to a bug introduced after that. EDIT: To add to this I would suggest you submit bug reports with logs so they can get this corrected, as this container is simply a template to use diginc's pihole container. https://github.com/diginc/docker-pi-hole/issues -- report issues here.
  17. Thanks! didn't know you could do that without breaking things in the container. Just upgraded - the bug I was having is indeed fixed, thank you!
  18. Just checking in to see if there is an ETA for the 1.7.5 release on Organizr yet? 1.75 did come out 8 days ago, not trying to rush it, just checking in since i know it fixes a bug i'm having.
  19. I was able to fix this by changing INTERFACE variable to eth0 as that seems to be what the docker container actually names the interface. things are running and working now it seems. Not sure why it worked on first launch with br0 picked but not 2nd launch, but this changed fixed it and i've started/stopped/forced updates and all is good. Note I also had to CHMOD the setupVars.conf file in order to edit it from my Windows machine using Notepad++, I wanted to change a few settings there. Namely these DNSMASQ_LISTENING=single DNS_FQDN_REQUIRED=false DNS_BOGUS_PRIV=false DNSSEC=false
  20. I'm currently getting the following issue - this is a new setup for me, and I had things working, added a few whitelists from my old Pi.Hole config and restarted and it doens't seem to actually want to block anything or process queries now. dnsmasq: warning: interface br0 does not currently exist br0 is what it is bound to on my docker container network type, br0 with 10.0.0.20 and the variable for INTERFACE is also set to br0.
  21. Figured out what I was doing wrong. Leaving config here for anyone that needs to do something similar in the future. The websockify needs to be port 7910, while the vnc itself is 7810. Oops! Also the "auth_request" portion of this config is only if you're using Organizr with server-auth configured. Comment those lines out otherwise. # CRASHPLAN CONTAINER location /websockify { auth_request /auth-admin; proxy_pass http://10.0.0.10:7910/; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; proxy_set_header Host $host; proxy_read_timeout 61s; proxy_buffering off; } location /crashplan/ { auth_request /auth-admin; proxy_pass http://10.0.0.10:7810/; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; proxy_set_header Host $host; }
  22. Ok so I understand what you mean now @Djoss, here's my current config and the error I'm seeing. Still getting an error when the websocket goes to make the connection, gets error 200, so something is still off. # CRASHPLAN CONTAINER # NOT CURRENTLY WORKING # location /crashplan/ { # auth_request /auth-admin; # proxy_pass http://10.0.0.10:7810/; # proxy_http_version 1.1; # proxy_set_header Upgrade "$http_upgrade"; # proxy_set_header Connection "upgrade"; # proxy_read_timeout 86400; # } # NEW TESTS BELOW location /websockify { proxy_pass http://10.0.0.10:7810/; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; proxy_set_header Host $host; proxy_read_timeout 61s; proxy_buffering off; } location /crashplan/ { proxy_pass http://10.0.0.10:7810/; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; proxy_set_header Host $host; }
  23. Super new to nginx and reverse proxying, so maybe I'm missing something but this isn't working for me? I just keep getting bad gateway or if I do get anything to load it's the VNC wrapper that shows it's disconnected and the image is broken in the top left too. If you know what I'm doing wrong let me know, would be very helpful, thanks!
  24. Is there a way I can reverse proxy to this container? I want to be able to check it from the outside when I'm logged into Organizr. I'm not sure what kind of VNC web service it's using so I haven't been able to find a working config. Thanks!
  25. Thanks for the update, working great again now. Hope whatever is in your plate isn't bad stuff!
×
×
  • Create New...