Apache Virtual Host: Starting httpd: AH00112: Warning: DocumentRoot [/var/www/html/..............] does not exist

When trying to create  VirtualHost on Apache it get the following error on restart of htttpd

sudo service httpd restart

Stopping httpd:                                            [  OK  ]
Starting httpd: AH00112: Warning: DocumentRoot [/var/www/html/dstubblefield.com\xe2\x80\x9d] does not exist
                                                           [  OK  ]

I have created the vhost.conf  in  /etc/httpd/conf.d/vhost.conf and added the following and saved.

<VirtualHost *:80>
ServerAdmin drew@dstubblefield.com
DocumentRoot "/var/www/html/dstubblefield.com”
ServerName dstubblefield.com

The folder /var/www/html/dstubblefield.com was created with permissions 775

There must be something simple that I am missing - Thanks
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Check permissions on all the folders on the path. If apache user don't have execute permissions on any of the folders in the path, then the file can't be reached.
drewsfotoAuthor Commented:
On the folder path, /var/www/html/dstubblefield.com all folder permissions are 775, so we have the execute permissions on that folder path.

/var permissions are 775
/www permissions are 775
/html permissions are 775
/dstubblefield.com permissions are 775
Jan SpringerCommented:
Check that you don't have special characters at the end of the document root host statement.
The 7 Worst Nightmares of a Sysadmin

Fear not! To defend your business’ IT systems we’re going to shine a light on the seven most sinister terrors that haunt sysadmins. That way you can be sure there’s nothing in your stack waiting to go bump in the night.

Also maybe you can check the logs just in case there is another clue of what could be happening. Also check that the spelling of the path don't have any mistake.
drewsfotoAuthor Commented:

Checked no special characters  at the document root host statement.

The spelling of the path is correct, I must have checked that a hundred times.
what about the ending \xe2\x80\x9d part? It looks like there are some strange characters at the end of this line. Maybe there are not visible characters. Try to remove them (remove until this line and the following line are merged and then put the return again).

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Jan SpringerCommented:
exactly.  like maybe a copy/paste that's gotten out of hand.  try manually typing them [again].
drewsfotoAuthor Commented:
Thanks so much
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Apache Web Server

From novice to tech pro — start learning today.