-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
curl: (52) Empty reply from server #905
Comments
Are you behind a proxy? If that's the case you may need to modify |
No, I'm using curl from the same machine as postgrest is running on, although the postgresql server is elsewhere. There's no requirement that postgrest run on the same host as postgresql? |
No requirement, postgREST doesn't need to run in the same host as postgresql server. |
% Total % Received % Xferd Average Speed Time Time Time Current 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0* Trying 127.0.0.1...
0 0 0 0 0 0 0 0 --:--:-- 0:00:01 --:--:-- 0* Empty reply from server 0 0 0 0 0 0 0 0 --:--:-- 0:00:01 --:--:-- 0
|
@twistedlizard can you enable db logging and see what queries your web requests trigger? There are instructions for how to do this here: https://postgrest.com/en/v4.1/admin.html#debugging |
this is either a firewall issue. closing until more detail is given |
I'm having the same issue. This is my log:
|
Downgrading to 0.4.0.0 fixes the issue. I'm using the 32 bit version. Problem occurs in 0.4.1.0 to 0.4.3.0 |
... Forgot to write that it's the 32 bit Ubuntu version we're using. |
Due to the multiple reports of this issue I'm reopening it for further examination. |
We had a report of this happening intermittently on a Rasberry Pi, don't know exactly why this happens but thanks to the hint by @Gameengine1 (not happening on 0.4.0.0) I managed to solve the issue by reverting this change #834 which changed a connection timeout default. |
In my case (PostgREST 0.5.0.0 via brew) it was because port 3000 was already in use and PostgREST didn't fail or warn as I would have expected. |
Latest v6* versions should have this definitely resolved since we don't mess with SIGHUP anymore. |
For anyone bumping into this, the issue could be an nginx conf, see #1399 (comment). |
curl: (52) Empty reply from server |
@NushratRia What's your OS and PostgREST version? |
Also, is the OS 32 bit? I had the same problem and it was gone when changing the same ubuntu to 64 bit. |
please reopen problem persists on raspberry pi 4 |
@xevilstar Sure. I'll reopen. Can you share the output of |
Please somebody redirect me if this isn't the best place for this question.
I couldn't get postgrest to work on the windows server I use (see other thread) so I've installed it on linux instead. Now, I'm following Tutorial 0.
I have a database, schema, table, roles & permissions all set up on a remote postgresql server, as per the tutorial. From the linux machine I'm testing on, I can connect to that remote postgresql server using, for example, PgAdmin3.
postgrest seems to start ok
Then, attempting to use curl in another terminal window
could anyone suggest how I can fault find?
postgrest 0.4.2.0
postgresql 9.6.3
The text was updated successfully, but these errors were encountered: