jwt is invalid after #255 about charm HOT 8 CLOSED

hey, sorry for the delay, #286 should fix it!

from charm.

it works!! thank you again!! my intuition is that the change made it try to use rsa key type instead of eddsa/ed25519? that was as far as i'd kinda figured out, but looking at the pr, i think i'd have been stuck a long time before figuring out how to fix without just fully reverting the whole thing.

thanks again 👍

from charm.

seeing in this example it's hitting ::1, i've had mixed results with ipv6 to begin with but in my original testing where i hit this bug i was either using 127.0.0.1, my exact ipv4 ip, or my tailnet dns address which i think is ipv4.

from charm.

this is at least also true when using wsl ubuntu 22 for both client and server sides

OS [e.g. Ubuntu, macOS]
ubuntu 22.04 by way of wsl 2 by way of windows 11
Shell [e.g. zsh, fish]
pwsh 7
Terminal Emulator [e.g. kitty, iterm]
windows terminal
Terminal Multiplexer [e.g. tmux]
none

PS /mnt/c/Users/drewr/charm> cat /etc/os-release
PRETTY_NAME="Ubuntu 22.04.3 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04.3 LTS (Jammy Jellyfish)"
VERSION_CODENAME=jammy
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=jammy

from charm.

Seeing the same problem on ubuntu 22 with a fresh install.

from charm.

@caarlos0 if you have time i'd like to help resolve this if i can. do you have any suggestions for what might be needed? this has been a blocker for me for a little bit and i have just now gotten back around to looking at it.

from charm.

maybe it's something else? i tried building from the latest release even and i'm not able to connect to localhost anymore idk what changed.

from charm.

you're a lifesaver! thank you so much!! testing now 🤓

from charm.