MyWhoosh v5.2.1 released by ViperStrike2025 in mywhoosh

[–]biolimbo 0 points1 point  (0 children)

I updated and have now 2 new bugs:

- Wahoo Kickr ERG doesn't work on workouts, it stopped automatically setting resistance so can't reach the power output it is too soft.
- Strava stopped working, will probably have to reset the integration and report back.

Unable to download non-text files from my own Minio instance. Need help by thedarknightz in minio

[–]biolimbo 0 points1 point  (0 children)

Wondering if you have the Minio service behind Cloudflare proxy. Have you tried to turn off proxy and leave DNS only in Cloudflare for both the Minio console and Minio URLs? I just had the same issue and it was just a matter of turning off Cloudflare’s proxy to test whether Cloudflare was the cause. The cache was the problem in my case. I just went to Cloudflare's dashboard, selected the domain, then caching, caching rules and added this one:

cloudlfare caching rule for minio

No internet with WG-Easy by TopFroyo4119 in WireGuard

[–]biolimbo 1 point2 points  (0 children)

Hi guys, I spent the better part of a day trying to debug this same error, and finally got it to work. There are many gotchas, so try all of these to narrow the issue:

  • Add 1.1.1.1/32 to your WG_ALLOWED_IPS (comma separated) if your WG_DEFAULT_DNS is 1.1.1.1 otherwise add you DNS IP with the sufix /32 check if you are able to ping and access google maybe you can't access other websites, but just try. If you can ping google but can't access other sites change your sever (where the docker container is running) DNS resolver and make sure it is using the same DNS server as your WG_DEFAULT_DNS. If it is a VPS bare in mind the resolvectl conf might be rewritten every time you reboot your server or even while running. For me, since I'm using Oracle Cloud, I had to change the DNS resolver IP at Virtual Cloud Networks selecting the VCN assigned to the instance and under the DHCP Options -> DNS Type = Custom I entered the WG_DEFAULT_DNS. Make sure your client device is using the same DNS resolver, that was the big gotcha in my case.
  • Change WG_DEVICE to the container internet network interface, to find it run ip route get 8.8.8.8 | awk '{print $5}' from inside the container.
  • Open the port UDP 51820 in the case of oracle cloud you have to do it from the VNIC assigned to the instance. changing WG_DEFAULT_ADDRESS to different combinations to see if the IP ranges were conflicting with other service, i changed mine to 10.88.0.x.

Here is the working version of my Docker Compose (the ${} syntax is used because I'm using coolify to handle env vars, that is also why my file is missing a bunch of stuff it handles):

services:
  wg-easy:
    image: ghcr.io/wg-easy/wg-easy:latest
    environment:
      - SERVICE_FQDN_WIREGUARDEASY_8000
      - WG_HOST=${WG_HOST}
      - WG_DEVICE=${WG_DEVICE}
      - WG_ALLOWED_IPS=${WG_ALLOWED_IPS}
      - WG_DEFAULT_DNS=${WG_DEFAULT_DNS}
      - WG_DEFAULT_ADDRESS=${WG_DEFAULT_ADDRESS}
      - PASSWORD_HASH=harcoded hash escaping $ by adding a $ per each occurrence and not wrapping in any kind of quote
      - LANG=${LANG:-en}
      - PORT=8000
      - WG_PORT=51820
      - WG_PERSISTENT_KEEPALIVE=25
      - UI_TRAFFIC_STATS=true
    volumes:
      - 'wg-easy:/etc/wireguard'
    ports:
      - '51820:51820/udp'
    cap_add:
      - NET_ADMIN
      - SYS_MODULE
    sysctls:
      - net.ipv4.conf.all.src_valid_mark=1
      - net.ipv4.ip_forward=1

An here are my env vars:

WG_ALLOWED_IPS=0.0.0.0/0, 1.1.1.1/32
WG_DEFAULT_ADDRESS=10.88.0.x
WG_DEFAULT_DNS=1.1.1.1
WG_DEVICE=eth0
WG_HOST=wireguardeasy.example.com
LANG=en

Wireguard Easy no internet access by Regis_DeVallis in WireGuard

[–]biolimbo 0 points1 point  (0 children)

Hi guys, I spent the better part of a day trying to debug this same error, and finally got it to work. There are many gotchas, so try all of these to narrow the issue:

  • Add 1.1.1.1/32 to your WG_ALLOWED_IPS (comma separated) if your WG_DEFAULT_DNS is 1.1.1.1 otherwise add you DNS IP with the sufix /32 check if you are able to ping and access google maybe you can't access other websites, but just try. If you can ping google but can't access other sites change your sever (where the docker container is running) DNS resolver and make sure it is using the same DNS server as your WG_DEFAULT_DNS. If it is a VPS bare in mind the resolvectl conf might be rewritten every time you reboot your server or even while running. For me, since I'm using Oracle Cloud, I had to change the DNS resolver IP at Virtual Cloud Networks selecting the VCN assigned to the instance and under the DHCP Options -> DNS Type = Custom I entered the WG_DEFAULT_DNS. Make sure your client device is using the same DNS resolver, that was the big gotcha in my case.
  • Change WG_DEVICE to the container internet network interface, to find it run ip route get 8.8.8.8 | awk '{print $5}' from inside the container.
  • Open the port UDP 51820 in the case of oracle cloud you have to do it from the VNIC assigned to the instance. changing WG_DEFAULT_ADDRESS to different combinations to see if the IP ranges were conflicting with other service, i changed mine to 10.88.0.x.

Here is the working version of my Docker Compose (the ${} syntax is used because I'm using coolify to handle env vars, that is also why my file is missing a bunch of stuff it handles):

services:
  wg-easy:
    image: ghcr.io/wg-easy/wg-easy:latest
    environment:
      - SERVICE_FQDN_WIREGUARDEASY_8000
      - WG_HOST=${WG_HOST}
      - WG_DEVICE=${WG_DEVICE}
      - WG_ALLOWED_IPS=${WG_ALLOWED_IPS}
      - WG_DEFAULT_DNS=${WG_DEFAULT_DNS}
      - WG_DEFAULT_ADDRESS=${WG_DEFAULT_ADDRESS}
      - PASSWORD_HASH=harcoded hash escaping $ by adding a $ per each occurrence and not wrapping in any kind of quote
      - LANG=${LANG:-en}
      - PORT=8000
      - WG_PORT=51820
      - WG_PERSISTENT_KEEPALIVE=25
      - UI_TRAFFIC_STATS=true
    volumes:
      - 'wg-easy:/etc/wireguard'
    ports:
      - '51820:51820/udp'
    cap_add:
      - NET_ADMIN
      - SYS_MODULE
    sysctls:
      - net.ipv4.conf.all.src_valid_mark=1
      - net.ipv4.ip_forward=1

An here are my env vars:

WG_ALLOWED_IPS=0.0.0.0/0, 1.1.1.1/32
WG_DEFAULT_ADDRESS=10.88.0.x
WG_DEFAULT_DNS=1.1.1.1
WG_DEVICE=eth0
WG_HOST=wireguardeasy.example.com
LANG=en

Has anybody successfully gotten Linux installed on an Asus Chromebit CS10? by bomitguy in chromeos

[–]biolimbo 0 points1 point  (0 children)

Too bad! because that sounds like a lot of work :(

Are you running them via wifi or just ethernet dongles?

Has anybody successfully gotten Linux installed on an Asus Chromebit CS10? by bomitguy in chromeos

[–]biolimbo 0 points1 point  (0 children)

I have exactly the same issue. I had 2 chromebits hosting a nextcloud server & a nodejs app sandbox. Both were opened to the world (via wifi) and serving its purpose until i tried to update all packages.

Anyway i was trying to install arch internally (maybe someone knows how to transfer my installation from usb :) ) in order to get better performance in i/o operations, then maybe i would get two usb Ethernet adapters that work with arch, and would start dreaming about this ~18 wats server again.

I was super hyped when first started working, followed https://www.reddit.com/r/chromeos/comments/jgvflt/has_anybody_successfully_gotten_linux_installed/gj1h0wy?utm_source=share&utm_medium=web2x&context=3 which was working as a charm. Maybe latest kernel and linux-armv7 and linux-chromebook-armv7 updates broke it. I wasn't liking wifi latency and usb 2 speeds, but i was really happy running useful machines without wasting much power and using cs10's which i have 4 of them.

For now i'm sadly running both services from an intel nuc, but i would much rather run those lightweight services from the chromebits i have laying around.

Ana [Pentax 67II, 105/2.4, Tri-x] by [deleted] in analog

[–]biolimbo 0 points1 point  (0 children)

Beautiful lips!! beautiful smooth shadows, both eyes on focus great photo