rest request script does not work
I've just spun up a windmill instance on elest.io and want to make rest requests. But i cannot seem to get rest requests working at all, not even a call to https://google.at reurns anything. The Script starts loading and never finishes. I am using the unedited standard script when selecting the rest request script.
I've attached a screenshot of my script while it is loading.
Is that a configuration error in my instance or am i just missing some setting in windmill?
Google
Search the world's information, including webpages, images, videos and more. Google has many special features to help you find exactly what you're looking for.
9 Replies
Hi @Chaftalie , just to be certain, could you pull latest and let me know if you still have that issue
also could you share your script, and potentially try to reproduce on app.windmill.dev
Hi @rubenf thanks for the fast reply, I am using the standard script (I have not changed anything in the script)
// Fetch-only script, no imports allowed but benefits from a dedicated highly efficient runtime
export async function main() {
const res = await fetch("https://jsonplaceholder.typicode.com/todos/1", {
headers: { "Content-Type": "application/json" },
});
return res.json();
}
I am currently on CE v1.312.0-1-gc68cd9153, I see, that there is a new version (v1.316.0). I am using the image: ghcr.io/windmill-labs/windmill:main
which gets used for the worker and the server instance.
the lsp instance uses ghcr.io/windmill-labs/windmill-lsp:latest
should i change "main" to "latest" or something else?on the windmill demo account it works. the demo account also is on v1.312
Just saw that the demo instance has a other script, but its the same outcome with both scripts in both instances
there must be something wrong with the instance hosted on elest.io, maybe I have to ask their support, if there is something blocking outgoing rest requests?
they are using following docker file:
version: '3.7'
services:
db:
image: postgres:14
restart: always
volumes:
- ./db_data:/var/lib/postgresql/data
environment:
POSTGRES_PASSWORD: ${DB_PASSWORD}
POSTGRES_DB: windmill
windmill_server:
image: ghcr.io/windmill-labs/windmill:main
deploy:
replicas: 1
restart: always
ports:
- 172.17.0.1:8496:8000
environment:
- DATABASE_URL=postgres://postgres:${DB_PASSWORD}@db/windmill?sslmode=disable
- BASE_URL=https://${BASE_URL}
- RUST_LOG=info
## You can set the number of workers to > 0 and not need any separate worker service
- NUM_WORKERS=0
- DISABLE_SERVER=false
- METRICS_ADDR=false
windmill_worker:
image: ghcr.io/windmill-labs/windmill:main
deploy:
replicas: 3
restart: always
environment:
- DATABASE_URL=postgres://postgres:${DB_PASSWORD}@db/windmill?sslmode=disable
- BASE_URL=https://${BASE_URL}
- BASE_INTERNAL_URL=http://windmill_server:8000
- RUST_LOG=info
- NUM_WORKERS=1
- DISABLE_SERVER=true
- KEEP_JOB_DIR=false
- DENO_PATH=/usr/bin/deno
- PYTHON_PATH=/usr/local/bin/python3
- METRICS_ADDR=false
# to mount the worker folder to debug,, KEEP_JOB_DIR=true and mount /tmp/windmill
volumes:
- ./worker_dependency_cache:/tmp/windmill/cache
# - ./oauth.json/:/usr/src/app/oauth.json
lsp:
image: ghcr.io/windmill-labs/windmill-lsp:latest
restart: always
ports:
- 172.17.0.1:3001:3001
caddy:
image: caddy:2.5.2-alpine
restart: always
volumes:
- ./Caddyfile:/etc/caddy/Caddyfile
ports:
- 172.17.0.1:4580:80
# - 172.17.0.1:4443:443
environment:
- BASE_URL=${BASE_URL}
volumes:
db_data: null
worker_dependency_cache: null
I'm not sure, but it might be something specific to elest.io which I wouldn't recommend as a host provider, you will have a better time just hosting it on hetzner straight and using the official docker-compose
Looks like you're missing the
windmill_worker_native
, see https://github.com/windmill-labs/windmill/blob/08861c86def461a3696ceeab0ef7907f4561515c/docker-compose.yml#L65-L82GitHub
windmill/docker-compose.yml at 08861c86def461a3696ceeab0ef7907f4561...
Open-source developer platform to turn scripts into workflows and UIs. Fastest workflow engine (5x vs Airflow). Open-source alternative to Airplane and Retool. - windmill-labs/windmill
Thanks @Tiago Serafim for the info, I've just talked to Elestio and they added it to the docker-compose file of windmill. Now it works!
@rubenf Yeah, I'll probably move Windmill to hetzner at some point, are there any specific points why you cannot recommend Elestio to host opensource projects? I was thinking about using them as a "managed" hosting provider for my company in the future.
Just a heads up, not sure how they work, but the native workers have been a thing for a good while and using
:main
as tags is not a good way to host in production.
I mean, for a managed hosting, it doesn't look good@Chaftalie they say "managed" but it's not, and it doesn't provide much more than an out-of-date template compared to just our up-to-date docker compose
the only real managed windmill is provided by us, otherwise the second best is helm-charts/docker-compose