Jump to content

sdoksdlkk

Members
  • Posts

    4
  • Joined

  • Last visited

Posts posted by sdoksdlkk

  1. On 1/19/2018 at 12:31 PM, Squid said:

    Looks like the docker.img is corrupted.  Easiest to delete it and recreate it then re-add your apps via the apps tab, previous apps.

     

    Other problems.  Disk 1 has a ton of read errors   Personally, I'd replace it with 32 reallocated sectors, and 8 more waiting currently to be reallocated.

     

    Thank you, that helped fix some of the issues (delete docker.img) and rebuild.

     

    The only issue I'm having is my letsencrypt image is not working anymore. Does this have something to do with the new reverse proxy setup?

     

    Here's my log for when attempting to start the letsencrypt container. 

     

    Jan 22 12:37:22 Unraid kernel: docker0: port 6(veth91dec58) entered blocking state
    Jan 22 12:37:22 Unraid kernel: docker0: port 6(veth91dec58) entered disabled state
    Jan 22 12:37:22 Unraid kernel: device veth91dec58 entered promiscuous mode
    Jan 22 12:37:22 Unraid kernel: IPv6: ADDRCONF(NETDEV_UP): veth91dec58: link is not ready
    Jan 22 12:37:22 Unraid kernel: docker0: port 6(veth91dec58) entered blocking state
    Jan 22 12:37:22 Unraid kernel: docker0: port 6(veth91dec58) entered forwarding state
    Jan 22 12:37:22 Unraid kernel: docker0: port 6(veth91dec58) entered disabled state
    Jan 22 12:37:22 Unraid kernel: docker0: port 6(veth91dec58) entered disabled state
    Jan 22 12:37:22 Unraid kernel: device veth91dec58 left promiscuous mode
    Jan 22 12:37:22 Unraid kernel: docker0: port 6(veth91dec58) entered disabled state
    Jan 22 12:37:29 Unraid kernel: kvm: disabled by bios

     

×
×
  • Create New...