Topic: Virtual host alias: 404 for index.php

[Amplifiction]

Hello all,

Starting webdeveloper here, who wants to showcase a few websites to potential employers. To that end, I have set up a Linux (Mint) server and installed a LAMP stack on it, including SSL (CertBot) and ModSecurity.

I have set up a virtual host for my_domain.net. Browsing to https://my_domain.net successfully loads the index.html located under /var/www/my_domain.net.

I want to showcase a Laravel project, let's say under https://my_domain.net/laravel. For security reasons, I can't put the entire project under /var/www/my_domain.net/laravel. And so I have been trying to "link" the https://my_domain.net/laravel url to the 'public' subfolder of my project. I have tried to achieve this through symlinks and aliases. Since I would prefer to get this done with an alias, I'll be focusing on that method.

To rule out any problems originating in the complex Laravel project structure, I have created a /websites/test folder containing only a simple index.php file. (I have moved the 'websites' directory from my home folder to ensure that there are no ownership issues in the entire path.) The owner of the 'websites' folder and all of its contents is currently www-data, achieved by

[Stray78]

[Amplifiction]

[Amplifiction]

Solved by moving the Alias and <Directory> directives from
/etc/apache2/sites-available/my_domain.conf (virtual host config)
to
/etc/apache2/sites-available/my_domain-le-ssl.conf (virtual host config for https)

Also reverted back to <VirtualHost *:80> in my_domain.conf.

[James Blond]

[Amplifiction]

Why not use a simple password protection via Require user? [1][2]. Not need to change the other working config.


[1] https://httpd.apache.org/docs/2.4/mod/mod_authz_user.html
[2] https://httpd.apache.org/docs/2.4/mod/mod_auth_basic.html[/quote]

I'm not sure what you're suggesting. You mean putting the entire project under https://my_domain.net/laravel, and password protecting all files and folders there, except for the public folder? Wouldn't that still leave me with the challenge of making sure that browsing to https://my_domain.net/laravel opens https://my_domain.net/laravel/public/index.php? So I would still need an alias, I think?

On top of that, I have discovered a second challenge. While browsing to https://my_domain.net/laravel finally loads the /websites/laravel/public/index.php file, images and other pages are not found.

In the Apache access log, I see that a get request is being made for /images/x.jpg. When I compare this to the working /test alias I set up, this should be /laravel/images/x.jpg.

To clarify, my virtual host file contains two similar aliases. The only differences are the alias name, as well as the folder name.

[James Blond]

There are easy tutorials like https://www.slingacademy.com/article/how-to-run-laravel-in-a-subdirectory-of-a-domain/

Yes, that requires to modify the laravel config and the code.

[Amplifiction]

I solved this a few weeks ago, and realized I hadn't provided an update.

In the end I adjusted the code of the project. I also kept the alias. No other changes, like for example to .htaccess.

While I have seen tutorials/guides that (claim to) solve this problem for pure Laravel projects without changing the code, apparently this isn't possible with Inertia.

Using Inertia's shared data, I configured a prefix string ('/laravel') that I added in front of routes in my React components. At least this way, the prefix can be easily adjusted if it ever gets deployed to another website.

Thanks to everyone who took the time to help me.