musicking

Members
  • Content Count

    33
  • Joined

  • Last visited

Community Reputation

1 Neutral

About musicking

  • Rank
    Advanced Member
  1. Is it normal for this Docker Container to be 3GB? It doesn't look like it's a log issue.
  2. I keep getting XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-abc' in the logs, anyone else experience this? Seems to be happier after a fetch update and restart of container. Will monitor
  3. Can confirm, tried all the steps for wireguard with the same error. I will submit a github ticket when I have a chance.
  4. Looks like wireguard support is coming I tried setting the flag and importing the config, but I keep getting errors. I will wait a big longer and if you want more troubleshooting from me, let me know.
  5. Issue is fixed if you do the following: remove proxy_set_header Host $http_host; from your calibre-web.subdomain.conf Instead of the above, just remove /nginx/proxy.conf and restart letsencrypt docker
  6. No problem! Looks like someone submitted the issue: https://github.com/janeczku/calibre-web/issues/1477
  7. YES! I'm not the only one! Just edit the docker and use the 0.6.7 flag like shown in the picture
  8. Anyone experiencing issues with 068 update and nginx? The update seems to have broke things for me. Doesn't look like an issue with the docker image so much as 068 as when I downgrade the container it works and then if I upgrade within the container it breaks again.
  9. Anyone able to get the new document CODE server working in nextcloud 19 behind letsencrypt/nginx? I added the location ~ ^\/nextcloud\/(?:index|remote|public|cron|core\/ajax\/update|status|ocs\/v[12]|updater\/.+|oc[ms]-provider\/.+|.+\/richdocumentscode\/proxy)\.php(?:$|\/) { But still couldn't connect
  10. If anyone is having issues with the latest build, try updating 0.6.5-ls50 via the web interface and then use the latest docker image. This is working for me now, not sure if the docker image was fixed or if this fixed it.
  11. Anyone have any issues running the 0.6.6 version that just came out? Mine won't start and have since went back to 0.6.5 and was able to upgrade through the web UI. I can post logs and more info later if I'm the only one experiencing this.
  12. I don't think it's the router, I see the router logs passing the connection using the port forwarding rule...but then nothing. Edit: What is strange is the Wireguard Clients appear to connect just fine (no issue in the log). I'm not seeing anything connected via Unraid though (no handshake). I tried locally through a VM and it appears to work, but no updated handshake in Unraid. More Edits: Son of a B*tch....handshake just updated in the Plugin page and it's working. I have no idea what the "fix" was. This will forever bug me now that I don't know why it started working
  13. Not yet, I'm not home until later tonight. I will definitely test this though.
  14. net.ipv4.conf.wg0.accept_local = 0 net.ipv4.conf.wg0.accept_redirects = 1 net.ipv4.conf.wg0.accept_source_route = 1 net.ipv4.conf.wg0.arp_accept = 0 net.ipv4.conf.wg0.arp_announce = 0 net.ipv4.conf.wg0.arp_filter = 0 net.ipv4.conf.wg0.arp_ignore = 0 net.ipv4.conf.wg0.arp_notify = 0 net.ipv4.conf.wg0.bc_forwarding = 0 net.ipv4.conf.wg0.bootp_relay = 0 net.ipv4.conf.wg0.disable_policy = 0 net.ipv4.conf.wg0.disable_xfrm = 0 net.ipv4.conf.wg0.drop_gratuitous_arp = 0 net.ipv4.conf.wg0.drop_unicast_in_l2_multicast = 0 net.ipv4.conf.wg0.force_igmp_version = 0 net.ipv4.co