fresh install and php won't start

[Dave A]

here's my vhosts file. says error code 1 when i try to start php from admin:

Code: Select all

#
# Virtual Hosts
#
# If you want to maintain multiple domains/hostnames on your
# machine you can setup VirtualHost containers for them. Most configurations
# use only name-based virtual hosts so the server doesn't need to worry about
# IP addresses. This is indicated by the asterisks in the directives below.
#
# Please see the documentation at
# <URL:http://httpd.apache.org/docs/2.2/vhosts/>
# for further details before you try to setup virtual hosts.
#
# You may use the command line option '-S' to verify your virtual host
# configuration.

#
# Use name-based virtual hosting.
#
NameVirtualHost 127.0.0.1:80

<VirtualHost 127.0.0.1:80>
  DocumentRoot C:/xampp/htdocs/
  ServerName localhost
</VirtualHost>

NameVirtualHost *:80


<VirtualHOst *:80>

ServerName ec.localhost
DocumentRoot "C:xampp/ec/test"
ErrorLog C:/xampp/ec/logs/error.log
CustomLog C:/xampp/ec/logs/error.log common
<Directory "c:/xampp/ec/test">
Options Indexes FollowSymLinks
allow from all
order allow, deny
AllowOverride All
</Directory>
DirectoryIndex index.php index.html
</VirtualHost>

#
# VirtualHost example:
# Almost any Apach         


had trouble before but now new pc and starting with headaches 'cause i'm a newbie to xampp and don't know what i'm doing so if some one can help great.

[Wiedmann]

says error code 1 when i try to start php from admin:

You mean if you start "Apache" in the Control Panel?
--> Start Apache with the batchfile and read the error message.

[Dave A]

here'sthe batch file error:

Code: Select all

Diese Eingabeforderung nicht waehrend des Running beenden
Bitte erst bei einem gewollten Shutdown schliessen
Please close this command only for Shutdown
Apache 2 is starting ...
Syntax error on line 38 of C:/xampp/apache/conf/extra/httpd-vhosts.conf:
order takes one argument, 'allow,deny', 'deny,allow', or 'mutual-failure'

Apache konnte nicht gestartet werden
Apache could not be started
Press any key to continue . . .


.
can't see what's wrong about line #38 can u help?

[Wiedmann]

can't see what's wrong about line #38

"allow, deny" is not the same then "allow,deny".

[Dave A]

thanks but i'm confused exactly what do i insert in that line?
silly me.

[Dave A]

got it thanks surfed web for proper setup. umm when i try to launch the site my ff and chrome tell me i may be under attack? is that for real? or is it just a warning of possiblily?

[Wiedmann]

when i try to launch the site

Which site, the XAMPP demopage at "http://localhost/xampp/"?

[Dave A]

stops and warns before my local site: i get the xampp page fine and the status.

[Wiedmann]

So it's difficult to help:
I don't know anything about your site... (and if your site is attacking someone).

Maybe you want ask the authors from your browser, what is the exact meaning from this message and when this warning is raised?

[Dave A]

nope not attacking anyone. i'm not a threat to anyone. it happens as soon as i hit enter to view the site. all it does is say "hello dave" to make sure it's working. nothing beligerant nor threatening. how can i copy the message to post here?

[Dave A]

here's the message:
The site's security certificate is not trusted!
You attempted to reach ec.localhost, but the server presented a certificate issued by an entity that is not trusted by your computer's operating system. This may mean that the server has generated its own security credentials, which Google Chrome cannot rely on for identity information, or an attacker may be trying to intercept your communications. You should not proceed, especially if you have never seen this warning before for this site.

[Dave A]

here's the message:
The site's security certificate is not trusted!
You attempted to reach ec.localhost, but the server presented a certificate issued by an entity that is not trusted by your computer's operating system. This may mean that the server has generated its own security credentials, which Google Chrome cannot rely on for identity information, or an attacker may be trying to intercept your communications. You should not proceed, especially if you have never seen this warning before for this site.

here's the rest of the details: how do i make a certificate? or do i need to?
When you connect to a secure website, the server hosting that site presents your browser with something called a "certificate" to verify its identity. This certificate contains identity information, such as the address of the website, which is verified by a third party that your computer trusts. By checking that the address in the certificate matches the address of the website, it is possible to verify that you are securely communicating with the website you intended, and not a third party (such as an attacker on your network).

In this case, the certificate has not been verified by a third party that your computer trusts. Anyone can create a certificate claiming to be whatever website they choose, which is why it must be verified by a trusted third party. Without that verification, the identity information in the certificate is meaningless. It is therefore not possible to verify that you are communicating with ec.localhost instead of an attacker who generated his own certificate claiming to be ec.localhost. You should not proceed past this point.

If, however, you work in an organization that generates its own certificates, and you are trying to connect to an internal website of that organization using such a certificate, you may be able to solve this problem securely. You can import your organization's root certificate as a "root certificate", and then certificates issued or verified by your organization will be trusted and you will not see this error next time you try to connect to an internal website. Contact your organization's help staff for assistance in adding a new root certificate to Windows.

[Wiedmann]

The site's security certificate is not trusted!

So you are opening your site with "https://" instead of "http://"?

[Dave A]

yes; does it matter which one i use?

[Wiedmann]

does it matter which one i use?

If there would be no difference between "http://" and "https://", it would make no sense that you have both.

Well "https" is for encrypted connections and XAMPP is only shipped with a test certificate. If you need a real certificate, you must by one. (or trust/import the test certificate in your browser)