Don Cezar
Explore posts from serversCDCloudflare Developers
•Created by Don Cezar on 10/19/2024 in #general-help
502 bad gateway
So it turns out the browser is not at fault but the user's IP?
If the website doesn't load for an user, even fetching it with Node will return an error, but as soon as they use the mobile data from their phone, it suddenly loads?
3 replies
CDCloudflare Developers
•Created by Don Cezar on 10/19/2024 in #general-help
502 bad gateway
A second user now reported this issue.
1. First user using Chrome on iOS
2. Second user using Chrome on Windows 10
3 replies
DTDrizzle Team
•Created by Don Cezar on 9/2/2024 in #help
Drizzle Studio stuck at 'connecting to localhost:4983'
Is it possible to manage multiple databases in the same drizzle studio instance? Connecting to
postgres://postgres:postgres@localhost:5432 defaults to the postgres database (at postgres://postgres:postgres@localhost:5432/postgres)71 replies
DTDrizzle Team
•Created by Don Cezar on 9/2/2024 in #help
Drizzle Studio stuck at 'connecting to localhost:4983'
npx drizzle-kit studio --host 192.168.100.14
https://local.drizzle.studio/?host=192.168.100.1471 replies
DTDrizzle Team
•Created by Don Cezar on 9/2/2024 in #help
Drizzle Studio stuck at 'connecting to localhost:4983'
Adding the host in the command and visiting the right URL seems to make it work, I guess?
71 replies
DTDrizzle Team
•Created by Don Cezar on 9/2/2024 in #help
Drizzle Studio stuck at 'connecting to localhost:4983'
It doesn't have a 'secure connection' (no ssl) but it works I think
71 replies
DTDrizzle Team
•Created by Don Cezar on 9/2/2024 in #help
Drizzle Studio stuck at 'connecting to localhost:4983'
No idea...
71 replies
DTDrizzle Team
•Created by Don Cezar on 9/2/2024 in #help
Drizzle Studio stuck at 'connecting to localhost:4983'
It suddenly started working
71 replies
DTDrizzle Team
•Created by Don Cezar on 9/2/2024 in #help
Drizzle Studio stuck at 'connecting to localhost:4983'
Wait
71 replies
DTDrizzle Team
•Created by Don Cezar on 9/2/2024 in #help
Drizzle Studio stuck at 'connecting to localhost:4983'
You mean where I run the npx studio command yeah? Nope, no errors
71 replies
DTDrizzle Team
•Created by Don Cezar on 9/2/2024 in #help
Drizzle Studio stuck at 'connecting to localhost:4983'
So there's something working, just not properly
71 replies
DTDrizzle Team
•Created by Don Cezar on 9/2/2024 in #help
Drizzle Studio stuck at 'connecting to localhost:4983'
Turning the url from
http://192.168.100.14:4983 to https://192.168.100.14:4983 (https) turns the page from didn't send any data to 404 Not Found71 replies
DTDrizzle Team
•Created by Don Cezar on 9/2/2024 in #help
Drizzle Studio stuck at 'connecting to localhost:4983'
When specifying the host in the command the server does start, going to
localhost:4983 turns from 192.168.100.14 refused to connect. to 192.168.100.14 didn’t send any data., but I'd need to make it work without forwarding ports71 replies
DTDrizzle Team
•Created by Don Cezar on 9/2/2024 in #help
Drizzle Studio stuck at 'connecting to localhost:4983'
How can I do this?
71 replies
DTDrizzle Team
•Created by Don Cezar on 9/2/2024 in #help
Drizzle Studio stuck at 'connecting to localhost:4983'
I'm not running it in docker
71 replies
DTDrizzle Team
•Created by Don Cezar on 9/2/2024 in #help
Drizzle Studio stuck at 'connecting to localhost:4983'
I can't make it work without exposing ports?
71 replies
DTDrizzle Team
•Created by Don Cezar on 9/2/2024 in #help
Drizzle Studio stuck at 'connecting to localhost:4983'
Expose? I thought Drizzle Studio can be ran completely locally
71 replies