vw-kombi

Members
  • Content Count

    215
  • Joined

  • Last visited

Community Reputation

5 Neutral

About vw-kombi

  • Rank
    Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I noticed the backups are smaller than my orginals. I have no idea why mine gained the extra files over time, likely not needed now. some are file system check files I believe. I may do the restore procedure and format of the USB to 'freshen it all up'
  2. I got it all working, had a play, then just removed the port forward so the remote stuff 'con's' are not there. More stuff may be added over time so I am happy to leave it as a glorified USB saving device until then. My remote access requirements are covered by tailscale to all my devices securely using wireguard (2FA linked to gmail) with no need of opening ports, firewall mods, ssl certs etc etc.
  3. With regards to port forwarding, am I able to enter the actual subnets that require forwarding, rather than anyone on the internet ? I currently only allow cloudflare IP's to access my home nginx server and re-direct that way. I have in the past used tailscale for access to unraid, and various other servers securely with zero config.
  4. This started happening to me as of today. My DNS however is set to cloudflares 'newer' 1.1.1.2 and 1.0.0.2 DNS servers. The ones with malware protection are 1.1.1.2. Maybe whatever unraid is using has got onto that list of nasties ?
  5. Been 4 days and no console crash. Fingers crossed it has settled down.
  6. Thanks for that - the first issue was waiting for me to climb in the loft of all places. I replaced my pfsense with ubiquiti USG (all on another thread as pfsense VM let me down), so I had to change the wifi's. This old laptop up in the loft is taking CCTV and storing it there every 5 minutes....... so robbers can be recorded and if they steal the unraid server, they are still on film. That is fixed now. Its just the console that is crashing. That support thing has not been an issue for me in the years of running unraid.
  7. Nope....... I assumed the diagnostics was wanted when the issue was in place. The issue causes no console, so I could not use the console to stop the array - or read the flash drive. In hindsight, I assume I could have figured out how to copy the diagnostics from the flash via the command line - as in I could cd to there, but not sure how I would have copied it off there.
  8. Oh dear - after restarting this c.php-fpm this time, all my console is white (not black) and in the top right I have 'missing key file' in red. If I click on that, and try to paste in my install key from the email from years back, I get Error (1) the bottom of the screen keeps f;ashing something about 'starting services', then warning something but it is too quick. to make matters worse, I cant stop the array as it says 'mover is running' to do a restart. In the end - a power off and on with the big button - and now the parity check I could do without !
  9. And this has happened again. While it was stopped, I took the liberty to again run the disagnistics from the command line. Pulled the flash drive and inserted it into the PC and copied the zip file to here as instructed. tower-diagnostics-20210329-1829.zip
  10. so this has happened again. This time, I just restarted php-fpm. root@Tower:~# /etc/rc.d/rc.php-fpm restart Gracefully shutting down php-fpm . done Starting php-fpm done root@Tower:~# This MUST be an issue with the latest unraid release - as I have never had this before. Do I raise this as an issue ? I just dont seem to get any replies. I seem to just be posting replies to my self.
  11. Ubiquiti USG is in and operational. Prob about 4 hours to move about 2 years of pfsense config/tweaking onto it. I must say I am loving the interface. VPN's requirements now being done with windows VM's. Was initially worried about the IDS/IPS limiting routing to 85Mbps, but I can still saturate my 100Mbps internet plan.
  12. more searching and then I found this which is the missing piece - whatever that is/does : /etc/rc.d/rc.php-fpm restart
  13. So.... broke out the kill command....... root@Tower:~# /etc/rc.d/rc.nginx stop Shutdown Nginx gracefully... root@Tower:~# ps -ef | grep nginx nobody 2725 9941 0 02:00 ? 00:02:16 nginx: worker process nobody 2726 9941 0 02:00 ? 00:00:25 nginx: worker process root 9243 1 0 Mar23 ? 00:00:00 nginx: master process /usr/sbin/nginx -c /etc/nginx/nginx.conf root 9244 9243 0 Mar23 ? 00:05:34 nginx: worker process is shutting down root 9935 9543 0 Mar23 ? 00:00:00 s6-supervise nginx root 9941 9935 0
  14. Seems it cant stop it : root@Tower:~# /etc/rc.d/rc.nginx stop Shutdown Nginx gracefully... root@Tower:~# /etc/rc.d/rc.nginx status Nginx is running root@Tower:~# /etc/rc.d/rc.nginx start Nginx is already running root@Tower:~# /etc/rc.d/rc.nginx status Nginx is running root@Tower:~#