Looks like you have a couple of items to look at in the fullstack1.conf file:
Your DocumentRoot should point to the directory that visitors to the site will start from which, based on the <Directory> entity, should be:
The final slash in the <Directory> entity is unnecessary:
Your programming language is obviously PHP, so it has nothing to do with Java, JDK, JDBC or whatsoever.
I am going to summarize two sources, because IMHO they are good enough so that it is not necessary to replicate everything here.
For PHP, the easiest way to go is to use Oracle Instant Client and PHP Database Object (PDO).
Summary from the Ubuntu Wiki:
I have different files with different owners, starting from the /var/www/* directory.
Files in /var/www/ need to be set to the user you use apache with. Otherwise you can run into permission issues and a website with potential security issues.
www-data was the default user for apache (v1). Nowadays apache (v2) uses apache as user and group. See your apache ...
I discovered the answer to my problems thanks to the answer to a previous question to this forum. The problem was that I needed to edit the php7.2.config file, which is found in the etc/apache2/mods-enabled folder, to allow me to store all my .php files in the public_html directory in the user (rather than root) space. So it was a permissions issue.
To allow ...
I tried the other answers here but this is the most complete solution I have found which worked for me:
$ sudo service apache2 stop
$ sudo apt-get purge apache2 apache2-utils apache2.2-bin apache2-common
$ sudo apt-get autoremove
The output of the below command will provide you with information the installed package software, version, architecture and short ...
but he's asking if there's a way for that folder (/home/username) can be owner writable and world readable for apache?
Please do not mess with home's permissions. If you want to go that route use a dedicated partition and change the permissions there. That is a lot more secure. I have had Windows users removing hidden files like .profile and .bash* because ...
Your screenshot with the response from sudo systemctl status apache2.service shows the error message:
AH00526: Syntax error on line 14 >
Invalid command 'WSGIScriptAlias'>
(You'll have to scroll left to see the remainder of the message.)
This tells you that you've got a syntax error in your Apache configuration.
It even tells you precisely where the ...
The logs aren't archived, or rotated, by the Apache HTTPd server itself, but by a separate tool called logrotate. Logrotate takes care of most logs. In addition to logs written by daemons like Apache HTTPd, MySQL or Postfix, it also rotates system logs like syslog, auth.log and so forth.
You may want to look into your logrotate configuration in /etc/...
If you want to use a catch all, you configure a _default that is used for any of your subdomains, if you have one certificate that covers both domains through a SAN subject alternative name or a wildcard certificate this will work.
There are a couple of things that you can try to have the domain name resolve as you'd like.
Remember IPv6 in /etc/hosts
# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback