Bolt.diy on Ubuntu 24.04 in Vmware | get no connection to bolt

bolt.diy [bolt.diy] Issues and Troubleshooting
1

I’m running bolt in a Vmware (Ubuntu 24.04 server).
Bolt starts and I get the message in Ubuntu for the URL
→ Local: http://localhost:5173/

This looks ok for me. No errors.

If I try to connect from the host system using the IP-Adress instead of localhost (‘localhost’ itself is also not working) I get no connection.

The network adapter is configured as NAT (I tried also bridged).

The message in Chrome says that the connection was refused by the vmware.

Does anybody has a idea?

Best Regards
neffetzz

2

Hi @neffetzz,

welcome.

I think you just need to expose the application to all:

pnpm run dev --host 0.0.0.0
1 Like
3

Great! That’s it. It works.

Now, I also know to handle the ‘–host’ parameter.

Greetings!

1 Like
4

I installed also Ollama in the same Ubuntu vmware like bolt.diy.
The modell ‘qwen2.5-coder’ was also loaded and is running.

How should I configure the URL for the local ollama installation?

image
image1621×832 65.2 KB

5

I assume you ask, because the configuration you got, is not working? :slight_smile:

Guess in the Dev-Console you see CORS-Errors
=> you need to setup an reverse-proxy on the VM and serve ollama with https
=> https:/, would then be the base URL

You can use nginx or caddy for example with self-signed certs.

Caddy Example:

6

I can‘t select the pulled Ollama models. :roll_eyes:

I try to install Caddy and then I give you a feedback.

1 Like
7

Hi,
now I’m back from holiday.
I have installed Caddy and it is running. I can access the vmware and no security warning appears.
I also have inserted two reverse_proxy rules to the Caddyfile.
Everything looks ok.

Thank you very much for your support.

Here is the code of the Caddyfile:


    admin off
    local_certs
}

neffetzz.de {
    bind 192.168.178.192
    tls internal {
        on_demand
    }
    log {
        output file /var/log/caddy/access.log
    }

    respond "Secure Caddy server - {host} - HTTPS Enabled!"
}

# Additional subdomains for different services
ollama.neffetzz.de {
    bind 192.168.178.192
    tls internal {
        on_demand
    }
    log {
        output file /var/log/caddy/ollama.log
    }
    reverse_proxy localhost:11434
}

# You can add more services following the same pattern
bolt.neffetzz.de {
    bind 192.168.178.192
    tls internal {
        on_demand
    }
    log {
        output file /var/log/caddy/bolt.log
    }
    reverse_proxy localhost:5173
}
1 Like