Title says it all. I have completed the required steps to enable the API services with no success.

The file ".htaccess" has been uploaded to the /api folder in my sites directory (/var/www/html/api). When I attempt to access this endpoint however I get the below error when clicking continue after. 

The API endpoint is not giving the expected response. Check you followed the instructions correctly. 
The URL being tested is: https://10.253.0.105/api/index.php?/core/hello

Can anyone help me figure out what is going on and why I cannot access this?

There are no log files or entries for the errored attempts to connect.
The system is running inside of a company VPN network.
The system has no custom folder structuring in the OS.

Is mod_rewrite and mod_setenvif enabled on your server? 

Apologies, how do I check that?

You would need to ask your hosting provider or server administrator as it is an apache module which needs to be enabled.

My server admin is walking into a meeting right now, I will get that information and update this post when it is available.

@Jim M here are the modules you asked about.

sudo httpd -M | grep rewrite_module
  rewrite_module (shared)
sudo httpd -M | grep setenvif_module
  setenvif_module (shared)

 

Would have them check to ensure they are working properly in your directory as if they are installed, they should be working.

those commands were all run from the root site directory. Should I be doing that from a different directory?

Thats something only your hosting company would be able to answer

@Marc Stridgen@Jim M thanks for helping out here these are in fact present and running not sure where the hangup is currently occurring.  Any suggestions?

 

 

1 hour ago, JonJones said:

@Marc Stridgen@Jim M thanks for helping out here these are in fact present and running not sure where the hangup is currently occurring.  Any suggestions?

 

 

Unfortunately, it being a local server and indeed an issue with a server environment, we are very limited on what we are able to assist with in this instance. Another cause I have seen are incorrect permissions on the index.php file, so that might be worth a check