Devtools doesn't load localhost api

[heyJonBray]

I'm setting up my first frame with frog, went to test out devtools but it will not load my frame into the devtools browser. This is a clean Next.js project on WSL2 (Ubuntu 20.04 on Windows 11).

"npm run dev" brings up http://localhost:3000/ with the default Next.js page.
"npm run frog-dev" brings up http://localhost:5173/ with the "Enter frame address" search bar in the center.

Enter https://localhost:3000/api into the nav bar, and I get the following error in my terminal:

  [running] frog@v0.8.2

  ➜  Local:   http://localhost:5173/
  ➜  Network: use --host to expose
(!) Could not auto-determine entry point from rollupOptions or html files and there are no explicit optimizeDeps.include patterns. Skipping dependency pre-bundling.
TypeError: fetch failed
    at Object.fetch (node:internal/deps/undici/undici:11576:11)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async Module.getImageSize (/home/jon/growth-cult/frames/quick-intel/qi-scanner/node_modules/frog/_lib/dev/utils/getImageSize.js:4:22)
    at async Promise.all (index 1)
    at async getInitialData (/home/jon/growth-cult/frames/quick-intel/qi-scanner/node_modules/frog/_lib/dev/api.js:278:19)
    at async eval (/home/jon/growth-cult/frames/quick-intel/qi-scanner/node_modules/frog/_lib/dev/api.js:54:29)
    at async dispatch (file:///home/jon/growth-cult/frames/quick-intel/qi-scanner/node_modules/hono/dist/compose.js:29:17)
    at async eval (/home/jon/growth-cult/frames/quick-intel/qi-scanner/node_modules/frog/_lib/dev/api.js:45:9)
    at async dispatch (file:///home/jon/growth-cult/frames/quick-intel/qi-scanner/node_modules/hono/dist/compose.js:29:17)
    at async file:///home/jon/growth-cult/frames/quick-intel/qi-scanner/node_modules/hono/dist/hono-base.js:188:25 {
  cause: Error: connect ECONNREFUSED 127.0.0.1:80
      at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1495:16) {
    errno: -111,
    code: 'ECONNREFUSED',
    syscall: 'connect',
    address: '127.0.0.1',
    port: 80
  }
}

I don't have any firewall rules that would be interfering, and the correct processes are running on the correct ports.

[dalechyn]

Do you enter https or http? Maybe that was an issue?

If still relevant, please comment.