Join the Webstudio community

Updated 3 weeks ago

Self hosting Builder (Locally) Help

Hey Fellow Web Studio Developers. I'm a newbie here. I've seen your post to Self host Builder locally inside Dev containers. I've taken the approach to use dev-container cli instead of running it through VsCode. I successfully ran through the final steps. but when I click the link it is not working.

The steps that I ran:
git clone https://github.com/webstudio-is/webstudio.git
npm install -g @devcontainers/cli
$ devcontainer up --workspace-folder webstudio/
$devcontaine exec --workspace-folder webstudio/ pnpm dev

I have attached the logs in the form of images .Any help would be appreciated.

Operating System : Linux(Void Linux)
node version: 23.10.0
npm version: 10.9.2
Docker version: Docker version 28.0.1, build tag v28.0.1
Docker-compose version: Docker Compose version v2.29.1
dev-container version: 0.75.0
Attachments
image.png
image.png
image.png
3
I
B
p
10 comments
Something with port forwarding or like. Nobody in dev team is using devcontainer directly or even linux. We can’t help here a lot. Try to find any devcontainers help about port forwarding or gpt chat as Im pretty sure it’s not a rare issue for any software
The app is running on 5173. Why do you think 3000 and 5432 can solve the problem?
In the above comments. somebody mentioned to perform portforwarding to see if the issue is fixed. I just tried that. After doing port-forwarding. localhost:3000 it return us object of values. But the app still runs on 5173 port.
May I know how to make webstudio working when I click the link which appears in the Network:"link"
you mentioned you're using dev container right. Normally when you click on the link it's supposed to open in your browser and you starts running the builder
@pradeep kumar if your on linux, cd into the .devcontainers folder and run docker compose up -d this will start up the devcontainers stuff and then from main folder run pnpm migrations migrate and after that run pnpm dev and see. this worked fine for me on fedora.
Thank you so much @VICTOR142 . It worked finally
@VICTOR142 since my port 5432 was already in use I tried setting the env variable of PGPORT to 5433 but when trying to migrate I got this error:
Plain Text
Authentication failed against database server at `localhost`, the provided database credentials for `postgres` are not valid.
I tried creating a container on port 5432 and it worked, the builder opened normally.

After I deleted the containers and rebuilt them again with port 5433 it didn't throw an error and worked normally, I assume that could be because of the 5432 instance creating a volume which then was reused by the 5433 one.
Add a reply
Sign up and join the conversation on Discord