#None of my sites are accessible, Laravel Forge

1 messages · Page 1 of 1 (latest)

brisk socket
#

Is the new update causing it?

glossy lantern
#

Forge 2.0 causing all of this. And noone from the team reacts to these issues. I already fighting with sin for about 48 hours, and nothing happes. Fuccrent forge release is full of issues. It should not be releases in current state.

crimson storm
#

Forge 2.0 shouldn't affect this as it didn't modify existing forge websites, just how the nginx configs etc are created.

Do you have your server IP and can you still access it with ssh/pinging it?

glossy lantern
#

You are very wrong, it does modify nginx config. If you have released sites on old config, and then add new site on new config everything just breakes, because tey incect new nginx configs on old servers.

#

I have tinkering my servers over SSH for a past few days to make things running once again, after Forge 2.0 was released and all of my sites goes down, after I added one site on server.

#

I have written some issues and how to fix them on Forge channel. I even send them su Forge support, but no one reacts:

Issue 1: SSL generation fails on Load Balancer

Error:
LetsEncrypt got an invalid response from "http://<DOMAIN>/.well-known/acme-challenge/<TOKEN>"

Research:
Investigated Nginx configuration and found that Forge no longer creates the letsencrypt-challenge.conf file.

Expected content of the file:
location /.well-known/acme-challenge {
auth_basic off;
allow all;
alias /home/forge/.letsencrypt;
}

Fix:
Manually created letsencrypt-challenge.conf in /etc/nginx/forge-conf/<site-id>/server/.
After this, SSL generation works correctly for a single domain.

Issue 2: Nginx breaks when adding multiple domains to site on load balancer

Error:
duplicate upstream

Research:
Found that Forge creates separate Nginx templates for each domain.
Each template includes the same upstream configuration, which causes the duplicate upstream error when forge restarts nginx.

Fix:
Temporary workaround: Restrict each site to a single domain to prevent the upstream conflict.

crimson storm
# glossy lantern You are very wrong, it does modify nginx config. If you have released sites on o...

yes, when deploying your server it does modify your nginx config.

But on a 1.5 year old server created in forge 1.0,

It did in fact not break existing sites and even allows me to have the existing sites and new sites co-exist on the same server without any problems.

My original nginx configs are still here, without any change.

That's why I'd go immediatly into just debugging if the server is still up and nginx didn't encounter any issues.

Immediatly going forge 2.0 broke this

glossy lantern
#

Well you are lucky, because all of my load balancers has been broken after 2.0 release.

#

Just try to add website to load balancer with multiple domains, and you will experience the same issue, because there is misconfiguration in forge deploy script that creates multiple upsreams, that breakes nginx.

subtle tusk
#

Hello I'm running into the same issue
I've been using forge.laravel.com for about 8 years now, I haven't deployed in a few months but trying now, none of my sites can deploy (or connect)
All sites exhibit the same errors

I've verified ssh keys, IPs, ports, etc but no luck

image.png
#

Oh never mind I see now a new IP was added