127.0.0.1:8000 isn't accesible

[kursad-k]

Hi
I can run lemonade on "http://localhost:8000/webapp.html#llm-chat" but not on "http://127.0.0.1:8000/webapp.html#llm-chat" This gives an error in GAIA as well since it is not able to acces "http://127.0.0.1:8000/webapp.html#llm-chat" I don't know what the issue is but I have no problem running server apps locally. I don't even understand why GAIA or Lemonade would make a distinction between these addres resolutions.

GAIA

❌ Error: Lemonade server is not running or not accessible.

Please start the Lemonade server first by:
  • Double-clicking the desktop shortcut, or
  • Running: lemonade-server serve

The server should be accessible at http://127.0.0.1:8000/api/v1/health
Then try your command again.

I am on Win 11 x64

thanks

[jeremyfowers]

Hi @kursad-k thanks for reporting. To quickly get unblocked you could run lemonade with lemonade-server serve —host 127.0.0.1

@kovtcharov: GAIA should be addressing lemonade at http://localhost:8000 not http://127.0.0.1:8000.

I definitely agree it would be better for either address to work, but I don’t think I’ll have cycles to investigate soon.

[kovtcharov]

This will be fixed in next release of Gaia. Thanks for the heads up!

[VladimirVLF]

localhost resolves internally to 127.0.0.1 which is IPv4 but can also resolve to IPv6 address ::1. The resolution is managed by /etc/hosts on Linux machines. Windows uses C:\Windows\System32\drivers\etc\hosts for that. It is internal DNS which is queried first for name resolutions.

It can be that your Windows resolves localhost to something else than 127.0.0.1.
It is better to use localhost both in Lemonade (already does) and GAIA (not yet) to be independent of the IPv4 vs IPv6.

[kursad-k]

Hi, Thanks for the reply. My system resolves localhost, the host file

# localhost name resolution is handled within DNS itself.
127.0.0.1       localhost
::1             localhost