Laravel Lighthouse-PHP GraphQL (Server cannot be reached)

Question

I'm using Laravel - Lighthouse-PHP GraphQL server, and when I deploy it to production, I have to write public in the URL in order to work:

https://example.com/graphql (Server cannot be reached) ✗
https://example.com/public/graphql (Server connected) ✓

My .htaccess contains the following:

RewriteEngine On
RewriteCond %{REQUEST_URI} !^/public/
RewriteRule ^(.*)$ /public/$1 [L,QSA]

while inside the public folder, there's another .htaccess file, contains the below:

<IfModule mod_rewrite.c>
   <IfModule mod_negotiation.c>
   Options -MultiViews -Indexes
   </IfModule>

   RewriteEngine On

   # Handle Authorization Header
   RewriteCond %{HTTP:Authorization} .
   RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]

   # Redirect Trailing Slashes If Not A Folder...
   RewriteCond %{REQUEST_FILENAME} !-d
   RewriteCond %{REQUEST_URI} (.+)/$
   RewriteRule ^ %1 [L,R=301]

   # Send Requests To Front Controller...
   RewriteCond %{REQUEST_FILENAME} !-d
   RewriteCond %{REQUEST_FILENAME} !-f
   RewriteRule ^ index.php [L]
</IfModule>

I tried editing(or removing) this file, but the whole website stopped working.

Any idea what I'm doing wrong?

"My .htaccess contains" - This `.htaccess` file is presumably in the document root? In which case it would seem this file is not doing anything. Are `.htaccess` overrides enabled for the root directory? "Server cannot be reached" - What is the exact error response/status? This sounds like a DNS error, but it can't be if `/public/graphql` connects? — MrWhite, Apr 10 '22 at 12:57
Yes, the first `.htaccess` is in my root folder, and .htaccess overrides is enabled. Server cannot be reached is graphql playground error if the graph link is broken. — Mohamed Shamoon, Apr 11 '22 at 15:27
Is the "graphql playground" expecting `/public` to be in the (visible) URL? That's really the only difference between those two requests. — MrWhite, Apr 11 '22 at 15:38
I tested sending mutations from my frontend website to https://example.com/graphql and it didn't work, I tried again to https://example.com/public/graphql and it worked. Maybe it's something related to the vendor location of lighthouse-php, wish one of them can see the question. — Mohamed Shamoon, Apr 11 '22 at 16:00

score 0 · Answer 1 · answered Apr 16 '22 at 16:01

In your webserver configuration make sure the root directory (the directory that is serving requests) is set tot the public folder instead of the root directory of your app as you have now.

You should only make the public folder publicly accessible, not doing so could result in an attacker to access or execute files they shouldn't or strange errors/behaviour (like what you are experiencing).

I also believe this will also fix the issues you are having since the public folder is not being rewritten which is probably picked up by the Laravel router for some reason.

I don't believe the issue is with Lighthouse but with how you are hosting your Laravel application, try and see if that can be fixed and if the problem persists.

Laravel Lighthouse-PHP GraphQL (Server cannot be reached)

1 Answers1