Topic: Apache2 only partially loading a page

[Obsdark]

Hello there,

I uploaded a laravel 10 project to an ubuntu 22 server with apache2, the thing is, just the starting position is showed by the laravel, the other ones are not and aren't even found at all by the apache.

the relevant parts of the apache2 config file are: https://hastebin.com/share/ohejewoyil.php

I suspect the apache2 is unable to find them but i don't know how to correct it, any suggestions or help?

Have a nice day

[James Blond]

IIRC Lavaravel requires the use of .htaccess files.
So instead of Options None You may allow overrides

[Obsdark]

Could you develop a little bit more?

Like, i just remove the "None" of the three related segments?

How can i apply what you suggest?

I ask this because i do remove all the "None" in the three blocks and it doesn't work

[James Blond]

replace the Options None with Options AllowOverride.
After that restart httpd (apache)

[Obsdark]

Doesn't work, it returns this error:

is an Ubuntu 22 if that matters at all

https://hastebin.com/share/paxigimacu.vbnet

[James Blond]

"allow from all" can be removed, that is the old syntax. "Require all granted" does the job in version 2.4.

Sorry, for the mistake.

Correct is

[Obsdark]

It doesn't work

I mean, it doesn't drop any error that stop it from work like before but doesn't fix the main issue that bring me here either, and the issue itself is very weird, let me show you with images maybe that help to have a clear picture about it:

This is the arriving page:

https://imgur.com/a/8e4XpiQ

This is Any other page after that:

https://imgur.com/a/VVPci47

And let me assure you than both pages work perfectly in local.

[James Blond]

It seems like mod rewrite is no loaded.

[Obsdark]

Can you develop a little bit what do you mean by that?

And how can i fix it?

[James Blond]

The 404 URLs are redirected to the index.php since those are only virtual paths that don't exist as files on the system. Like your "contracto" URL.

So you may try to enable mod_rewrite

[Obsdark]

[James Blond]

The easiest way is to add another vhost.

[Obsdark]

Try that, i experiment a little bit trying with another port and it doesn't work even when that port is actually open

https://hastebin.com/share/awirumufef.php

Any suggestions on how to do it?

Is there a way to do it by the name?

What other approaches do you know and recommend?

[tangent]

As James has said, you need to add another VirtualHost entry with appropriate ServerName directive(s), which looking at your hastebin shared configuration, you have done. Presume you added a second listen entry for port 81, so what does "httpd -S" produce? For me I get:

[Obsdark]

Ok perfect, i dig a little bit through the docs you send me but i have some question

How can i set the thing in order to being able to connect through a ServerName (or ServerAlias if apply) without the use of a DNS?

Is there even a way?

Is there a special way to indicate this to the browser so i can go to that other side instead of the default?

The VirtualHosts so far https://nopaste.linux-dev.org/?1338976

Bear in mind i'm in ubuntu 22 (if relevant)

[tangent]

Apologies, I should have noted you were on Ubuntu, not Windows.

So in which file have you placed your two VirtualHost entries? If it's /etc/apache2/apache2.conf, then you've not followed the recommended layout for configuration files on Ubuntu (Debian) - see the comments at the top of the apache2.conf file.

Split (move) your two vhost entries into suitably named site files, e.g.

/etc/apache2/sites-available/www.certera.test.conf
and
/etc/apache2/sites-available/other.certera.test.conf

Enable the sites and reload the Apache configuration

[Obsdark]

Given this as the document today: https://nopaste.linux-dev.org/?1338986

So, let me get this straight just to clarify

You say than i need to put one of those in one document and the other in another one, both of them in the folder sites-available as this:

/etc/apache2/sites-available/www.certera.test.conf

/etc/apache2/sites-available/other.certera.test.conf

and with nothing else

Then, i just write this commands:

$ sudo su -
# a2ensite www.certera.test.conf
# a2ensite other.certera.test.conf
# systemctl reload apache2

And that should be it?

If not and i miss something, i'll apreciate an indication about what i miss, or if it from that point on i need to do something else, i apreciate if you clarify it to me.

Another question:

How should i indicate in the url to enter one or the other project given the case than it is one ip?

For instance, if ip were, i don't know, 111.222.333.444, how can i connect to www.certera.test and to other.certera.test?

I ask this because i assume if i'm outside of that machine and/or network, like in the general internet for instance, i cannot connect directly using those urls without having that url linked through the DNS network of the internet to it am i right?

And if i'm wrong and i can, how exactly should i write it in the url bar on the navigator to enter one or the other projects?

Thank you for your time

[tangent]

To clarify and confirm:

1) Remove your two VirtualHost entries from apache2.conf
2) Split them into two separate files as described in the sites-available directory. I simply chose file names based on your ServerName entries.
3) Yes, run the commands as listed to enable those virtual host sites and restart Apache.

The "apache2 -S" command as shown should then confirm those virtual host sites are functional.

Re your second question, I tried to explain that you can use local host file entries to test your sites in the absence of official DNS entries on the internet.

So, if your Apache server IP is 111.222.333.444 then add test entries to /etc/hosts file on a (local) client machine where your test browser is, e.g.

# Test site entries.
#
111.222.333.444 www.certera.test
111.222.333.444 other.certera.test

That client browser should then be able to resolve requests such as http://www.certera.test, to the appropriate IP address, and connect to your Apache server. Apache will look at the host header in the HTTP request, pass the request to the corresponding virtual host site, and then return the appropriate content.

As you say, to access the sites remotely, you'll need appropriate external (routeable) IP DNS entries, as well as exposing your Apache server to the Internet.

There are numerous documents on the Internet covering the networking principles involved here, but such details and assistance in this area are beyond the scope of this site, which is primarily concerned with Apache web server and its configuration.

Good luck.