Jump to content

Brandonb1987

Members
  • Posts

    69
  • Joined

Posts posted by Brandonb1987

  1. 6 minutes ago, Brandonb1987 said:

    Let me clarify. pfsense is trying to offer that option address. So it’s going though. It doesn’t show up as a leased IP address.

     

    The VM hasn’t accepted it. 
     

    I cannot access home assistant vm through that address. 

    Sorry I was going to edit the reply but you sent one first

  2. I've been pouring over everything I can find for the last several hours. I cannot seem to get my Home Assistant (fresh install) VM to pull a network address from my routers dhcp.

     

    Yes i have the network bridged and bonded. All my dockers work on br0, but if i set the VM's network to br0, i can't seem to get an IP or local access to the VM.

     

    If i set it to Virtbr0, that gives a network address but I use 10.1.10.x/24 on br0 and virtbr0 is 192.x.x.x/24. And I can't access that either through the network. Tried using hostnames, nada.

     

    What do I need to do to get this working. I use pfSense as my network dhcp/dns server.

  3. getting an npm error in the nodered docker. When i try to update a pallet it gives me the following:

     

    Quote

    -----------------------------------------------------------
    2021-08-18T03:07:49.117Z Install : node-red-node-openweathermap 0.5.0

    2021-08-18T03:05:55.088Z npm install --no-audit --no-update-notifier --no-fund --save --save-prefix=~ --production --engine-strict [email protected]
    2021-08-18T03:05:56.881Z [err] npm
    2021-08-18T03:05:56.881Z [err]  WARN deprecated [email protected]: request has been deprecated, see https://github.com/request/request/issues/3142
    2021-08-18T03:05:57.142Z [err] npm
    2021-08-18T03:05:57.142Z [err]  WARN deprecated [email protected]: this library is no longer supported
    2021-08-18T03:05:58.379Z [err] npm 
    2021-08-18T03:05:58.379Z [err] WARN locking Error: EACCES: permission denied, open '/data/.npm/_locks/staging-accc372ed0ccb0d8.lock'
    2021-08-18T03:05:58.379Z [err] npm WARN locking  /data/.npm/_locks/staging-accc372ed0ccb0d8.lock failed [Error: EACCES: permission denied, open '/data/.npm/_locks/staging-accc372ed0ccb0d8.lock'] {
    2021-08-18T03:05:58.379Z [err] npm WARN locking   errno: -13,
    2021-08-18T03:05:58.379Z [err] npm WARN locking   code: 'EACCES',
    2021-08-18T03:05:58.379Z [err] npm WARN locking   syscall: 'open',
    2021-08-18T03:05:58.379Z [err] npm 
    2021-08-18T03:05:58.380Z [err] WARN locking   path: '/data/.npm/_locks/staging-accc372ed0ccb0d8.lock'
    2021-08-18T03:05:58.380Z [err] npm WARN locking }
    2021-08-18T03:05:58.442Z [err] npm ERR!
    2021-08-18T03:05:58.442Z [err]  code EACCES
    2021-08-18T03:05:58.442Z [err] npm ERR! syscall open
    2021-08-18T03:05:58.442Z [err] npm ERR! path /data/.npm/_locks/staging-accc372ed0ccb0d8.lock
    2021-08-18T03:05:58.442Z [err] npm ERR! errno -13
    2021-08-18T03:05:58.444Z [err] npm ERR! 
    2021-08-18T03:05:58.444Z [err] npm ERR! Your cache folder contains root-owned files, due to a bug in
    2021-08-18T03:05:58.444Z [err] npm ERR! previous versions of npm which has since been addressed.
    2021-08-18T03:05:58.444Z [err] npm ERR! 
    2021-08-18T03:05:58.444Z [err] npm ERR! To permanently fix this problem, please run:
    2021-08-18T03:05:58.444Z [err] npm 
    2021-08-18T03:05:58.444Z [err] ERR!   sudo chown -R 1000:1000 "/data/.npm"
    2021-08-18T03:05:58.452Z [err] 
    2021-08-18T03:05:58.452Z [err] npm ERR! A complete log of this run can be found in:
    2021-08-18T03:05:58.452Z [err] npm ERR!     /data/.npm/_logs/2021-08-18T03_05_58_445Z-debug.log
    2021-08-18T03:05:58.463Z rc=243

     I tried running the command in the console and just denies me.

     

    Any suggetions?

  4. 23 hours ago, binhex said:

    It is highly unlikely that you have the exact same issue, what you do have is the exact same symptom, there are literally dozens of reasons why the web UI is unavailable, please do the same as my previous post.

    Sent from my CLT-L09 using Tapatalk
     


    the only thing I’ve changed was I replaced duckdns with cloudflare but I did not change anything around Deluge. Again. Works totally fine with the VPN turned off. Can access it totally fine. Soon as I re-enable the VPN, can’t see the UI. 
     

    my log shows it starting everything just fine. Shows webui started, vpn connected, listening to privoxy port. 
     

    that’s the only issue. So do you want 2 logs one showing with vpn off and another with on? Or just on?

  5. I can confirm I have the exact same issue. I've been trying to fix it all week thinking it was maybe a port/dns/firewall issue. I've ruled it all out and lead me to here. Something is up with the VPN portion of PIA. I tried switching to the WireGuard implementation and it works without VPN turned on. Log shows no errors, just can't see the UI like reported.

  6. I've been having a problem for the last 2 weeks where I cant get Sonarr to connect to Deluge. It keeps giving me the error

     

    Unknown exception: The operation has timed out.: 'http://10.1.10.3:8112/json'

     

    Anyone else encounter this issue starting about 2 weeks ago? Was working perfectly fine up until then, and because I have automatic updates enabled I wont ever know when the issue exactly started.

     

    Any logs I can post to assist in finding a solution?

  7. Has anyone had issues with other non-admin users not being able to stream via chromecast? (in the last 2 weeks or so) It keeps giving everyone a "too many active streams" error when they try. It works on all apps and stuff but as soon as they try and use chromecast the error appears. 

     

    I've tried deleting both their profiles multiple times, made sure nobody else is using it, etc. I just can't figure this out. I feel it may be either a container issue or there's something that isn't closing itself down properly. If I go to the Dynamix Active Stream add-on, it has a list of Plex things but they can't be halted.

     

    Anyone got any theories?

  8. I’m thinking it’s the marvel based HBA as everything is happening to the first 8 drives only. That HBA is likely the culprit as you say. I’m going to order an LSI card and replace them both and run the memtest as a precaution. Hopefully that will fix it.

  9. I've had quite a few issues with my unraid the last few weeks. First drive 1 pooped itself and became read-only. Managed to get everything off it and put the data onto other disks before removing the drive and resetting the pool without it.

     

    After this was completed, I ran a scrub on all the disks (15/16 disks now) and found 5 files that were not correctable. I have since replaced/removed the files in favour of good copies. Hopefully this is fixed.

     

    I felt it was prudent to do a filesystem check on all the drives today since i've had so many problems and now I'm getting a few errors on 3/15 disks. What would be the best way to fix this? Should I do the same as I did to drive 1 (pull data off and place onto the good disks and reformat the disk)? Or can I simply pull the disk, format it, and reinstall and let it rebuild from parity?

     

     

    Part 2 of this issue: After having a read through the log, it appears this is really isolated to my first 8 drives which is all on 1 controller. Could the HBA be the cause for all these issues lately? Would it be a good idea to get it replaced? 

  10. I've tried everything to get stuff off disk 1 but i keep getting Input/output error with some files. I can't even copy certain ones out of my Snapshots because it appears they are corrupt as well.

     

    Suggestions?

     

    I purchased a new disk to replace it - suggestions?

  11. I just thought of something. I take daily snapshots of my Btrfs system. If I were to just pull disk 1, format it, and restore the files onto disk 1 from the snapshot, would that fix the issue? I’ve never had to restore files from a snapshot yet though so not entirely sure of the process

  12. So does the diagnostics show a dead/dying drive? If so I will order a new one

     

    or is there a way to fix the file system? If I were to run a pre-clear would that correct the issues after reformatting?

  13. Fun fact, rebooted the server and now Fix Common Problems alerted me of this error "Unable to write to disk1-Drive mounted read-only or completely full." - The disk is not full. I've had errors pop up from time to time on this disk. Could it be a disk related issue?

  14. Ok, but that doesn't solve the files/folder issue I have. That will fix the issue from getting worse.

     

    Googled for nzbget and its under UMASK and have to make it 000 to get a permission level of 777. I also found the section to change the file and folder permissions in Sonaar - set both to 777.

     

    How do I make everything in the share to 777 then? Follow my post above to change permissions then do the chown to make sure everything is under the proper nobody:users? Or is everything better to be put under root:root?

     

    I've tried "sudo chmod -R 777 /mnt/user/Media/" and all I get is this type of error for all the files

     

    "chmod: changing permissions of '/mnt/user/Media/Movies/The Mule.mp4': Read-only file system"

  15. Correct me if I'm wrong, but I believe this is what I need to do;

     

    1) sudo chmod -R 777 /mnt/user/Media/ (and do this for the other shares like /mnt/user/Download)

    2) sudo chown -R nobody:users /mnt/user/Media/ (and do this for the other shares like /mnt/user/Download)

     

    Would this fix all the issues?

×
×
  • Create New...