reworkd / AgentGPT

🤖 Assemble, configure, and deploy autonomous AI Agents in your browser.
https://agentgpt.reworkd.ai
GNU General Public License v3.0
31.29k stars 9.21k forks source link

http: invalid Host header #1450

Open BarryTheShen opened 7 months ago

BarryTheShen commented 7 months ago

Please check that this issue hasn't been reported before.

Expected Behavior

setup.sh run normally, and i can use AgentGPT

Current behaviour

When running setup.sh, after choosing Docker-compose (Recommended), it returns an error of http: Invalid Host headers.

Steps to reproduce

Run setup.sh

Possible solution

No response

Which Operating Systems are you using?

Acknowledgements

channingxiao18 commented 7 months ago

I had the same problem on the master branch. env files successfully created! [+] Building 16.6s (0/1)
[+] Building 17.2s (1/1) FINISHED
=> ERROR [internal] booting buildkit 17.2s => => starting container buildx_buildkit_default 17.2s ------nternal] booting buildkit 17.2s

[internal] booting buildkit:x_buildkit_default 17.2s

0 17.19 time="2024-01-19T06:40:19Z" level=warning msg="using host network as the defaultime="2024-01-19T06:40:19Z" level=warning msg="using host network as the default"

0 17.19 time="2024-01-19T06:40:19Z" level=warning msg="skipping containerd worker, as \"/run/containerd/containerd.sock\" does not exist"

dtime="2024-01-19T06:40:19Z" level=info msg="found 1 workers, default=\"i0a4m5z4b9deh8gvcie44di0n\"" `time="2024-01-19T06:40:19Z" level=warning msg="currently, only the default worker can be used." \time="2024-01-19T06:40:19Z" level=info msg="running server on /run/buildkit/buildkitd.sock" time="2024-01-19T06:40:19Z" level=warning msg="skipping containerd worker, as \"/run/containerd/containerd.sock\" does not exist"

0 17.19 time="2024-01-19T06:40:19Z" level=warning msg="currently, only the default worker can be used." => ERROR [internal] booting buildkit 17.2s

=> => starting container buildx_buildkit_default 17.2s

[internal] booting buildkit:

0 17.19 time="2024-01-19T06:40:19Z" level=warning msg="using host network as the defaultime="2024-01-19T06:40:19Z" level=warning msg="using host network as the default"

0 17.19 time="2024-01-19T06:40:19Z" level=warning msg="skipping containerd worker, as \"/run/containerd/containerd.sock\" does not exist"

0 17.19 dtime="2024-01-19T06:40:19Z" level=info msg="found 1 workers, default=\"i0a4m5z4b9deh8gvcie44di0n\""

0 17.19 time="2024-01-19T06:40:19Z" level=warning msg="skipping containerd worker, as \"/run/containerd/containerd.sock\" does not exist"

0 17.19 time="2024-01-19T06:40:19Z" level=warning msg="currently, only the default worker can be used."

0 17.19 time="2024-01-19T06:40:19Z" level=info msg="running server on /run/buildkit/buildkitd.sock"

0 17.19 time="2024-01-19T06:40:19Z" level=info msg="running server on /run/buildkit/buildkitd.sock"


0 17.19 time="2024-01-19T06:40:19Z" level=warning msg="currently, only the default worker can be used."

0 17.19


http: invalid Host header

channingxiao18 commented 7 months ago

after setting ENV variables, run DOCKER_BUILDKIT=0 docker-compose up --build manually, it succed to start. but there were still many warnings during image building.

BarryTheShen commented 7 months ago

What ENV variables did you tweak? I still can't get it working.

ToPGaMiSkS commented 7 months ago

how to deploy to vercel? i can't...