https://promptfoo.dev/ logo
Stuck on "Oops! You're lost!" in the promptfoo.app
# ❓|questions
a
Hi all, I ran into a problem while trying to generate credentials for sharing evals. I followed the instructions to go to promptfoo.app and set up an account. The verification email took some time to arrive, so I requested another one. When the email finally arrived, I entered the verification code, but it was invalid. Shortly afterward, I received another email with a different code. I had no way to repeat the procedure, and my account now only shows the "Oops! You're lost! You've wandered into an unknown part of our website." screen. I can only log out; every other action takes me to the same place. Thinking it was my fault for not waiting patiently for the queued verification codes, I tried again with another email address. This time, although I received only one code and entered it correctly, I still ended up on the same "You're lost" screen. Now I'm stuck with two accounts, set up with two different email addresses, both 100% unresponsive except for login/logout, and I still have no option to share my evaluations. Can you please guide me on what to do next? https://cdn.discordapp.com/attachments/1364134741841809408/1364134742206844958/image.png?ex=680890fa&is=68073f7a&hm=093ce96f3f5b1980feafb3eb80f369e3eb7bd4d6e5d9f362e65c62545d4a8e98&
u
@adanceofshells when you click go home what happens? Do you go to the same page?
Could you grab some time on my calendar to screen share? https://cal.com/steve-klein-10xzxs/secret
a
Hi Steve! Thanks for the reply. Clicking "Go home" would take me to the same page over and over. The URL was "/organizations/new". However, when I checked this morning, the issue was gone. I created a new organization and all the necessary screens are available. But I'm not all there yet - now I see
Authentication failed: fetch failed
when I try to log in using
promptfoo auth login
. Any idea what to do with this one?
u
I'm not sure, can you grab a screenshot of the full error message? Also to double check, are you copy and pasting the full login command with the api key?
a
The only output I get is
Authentication failed: fetch failed
with no additional context. I've been digging a little deeper and it turns out I can (usually) log in from a Docker container, but (usually) not from WSL. I was able to get a successful login message on WSL once (!), but after that
promptfoo share
failed with the message I'm attaching. I'm continuing to look for the environment differences between the container and my local setup, but it would be good to see a little more detailed output. https://cdn.discordapp.com/attachments/1364134741841809408/1364609998335770746/image.png?ex=680a4b98&is=6808fa18&hm=1600b58ece3dfe43073065f171fc1d13c46a9dfdae148622888dcd658a55072f&
Hi @[Promptfoo] Steve , I wanted to provide an update. I managed to trace back my problems with the
fetch failed
error to a DNS server configuration in my WSL. It turns out that the resolver queries the DNS server for the IPv6 address of api.promptfoo.app, which it doesn't obtain. Consequently, the additional DNS resolution time exceeds the hard-coded timeouts (I believe it's 10 seconds for https://api.promptfoo.app/health). For now, I have reduced the number of retries by the DNS resolver to ensure the entire request stays within the 10-second window, and I managed to get it working. However, it might be a good idea to allow users to override these timeouts?
u
Thanks for letting me know!