Cant access wireguard UI
The bcrypt password hash does not seem to work, and I cannot access the UI to set up clients. A couple weeks ago I set up wg in a VM (running on Debian 12) and all worked well. Now, installing on new server following same process (use bcrypt site to generate hash using defaults - bcrypt method, 12 rounds) password is not accepted. Tried several times. Verified hashes verify against passwords on bcrypt site. Oddly, the old hash from previous working install works on new install. Anybody seen anything like this ?
2 Replies
Hello check this it’s related to your problem https://github.com/runtipi/runtipi-appstore/issues/4747
GitHub
🐛 [WireGuard Easy] bcrypt PASSWORD_HASH exceeds character limit due...
Store Application WireGuard Easy (wg-easy) App version 14 Description The issue arises when configuring the PASSWORD_HASH environment variable for wg-easy through the RunTipi interface. According t...
Not sure if this is related. Both working and non-working hashes appear very similar WRT $ character. The following working and non-working hashes both verify to "Adm1nmenow!", but only one will authenticate with wg-easy. Internal container bug ?
$2y$12$5TxSi8MvyURNbdHeL1bhUecBluQlkdI/T6CPqpvkMhJvempMZ7k7i - works
$2y$12$g/0zj04wucjJCIczPIDGcuUv9EBorOUhlq9tILYk5cNHBsW7GCCVC - not work
I'm not sure how runtipi processes things, but I notice that the app.env file in app-data sets WIREGUARD_PASSWORD_HASH=<hash>. If this is processed by bash, the $ symbols will invoke expansion and corrupt the value. Maybe should be in single quotes ?