Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.

IsaacBen's avatar

This site cannot be reached took too long to respond err_connection_timed_out

Hey, I have a Laravel app in DigitalOcean, which was installed via Forge in last December. It runs on Ubunutu 14 on the $20 plan. Only one user uses the site as it's an admin system. In the last week I get that error sometimes once or more a day, and sometimes not at all. Any idea what might cause this? Usually after a couple of minutes when it happens site is fine.

I haven't touched the server, didn't update anything so I can't figure out what might cause this issue suddenly after several months of no problems at all.

0 likes
7 replies
IsaacBen's avatar

All error logs are empty except "default-error.log.1". It has some weird errors that I don't understand.

FastCGI sent in stderr: "Unable to open primary script: /home/forge/default/public/testproxy.php (No such file or directory)"
FastCGI sent in stderr: "Unable to open primary script: /home/forge/default/public/command.ph

I don't have those files in public folder. Why is it looking for them?

abdulmalik67's avatar

@Paguemaou I got the same error after adding and removing a firewall rule in Forge.

See the post here:

Did you get the same error?

IsaacBen's avatar

@Paguemaou I have the same error, but my site works for the most part, and I haven't changed any Firewall rules. It just happened for some reason.

cakka's avatar

I am also experience this problem. Did you get the solution ?

IsaacBen's avatar

@cakka It got solved by itself at some point. No idea what it was and what caused it.

Please or to participate in this conversation.