bob95825

Thanks for the reply Dharmesh. I did a lot more troubleshooting. I re-pointed my https://abc.com to the shared host where it worked with the other domain, but it still didn’t work. Then I looked at the code and tried sending API requests in Postman to https://wp-site/wp-json/edwiser-bridge/wisdmlabs/. Figured out there was an extra space in the token (I did this after re-pointing). Removing the extra space worked on the shared host. So re-pointed the domain to AWS and tried again and immediately, on postman, saw that wp-json wasn’t working (404 error).

Finally figured out it was a setting in the Apache server blocking access to the .htaccess file in the wordpress directory, thus rewrite engine not routing anything, which led to the error. My only suggestion here for improvement is instead of the generic error message, maybe you should include the actual response from the server so it’ll be easier to debug. If I had seen the “404 not found” as a response from the EC2 server, I would have worked only to look for the fix on AWS instead of trying a variety of things. It would have saved me a lot of time.

Maybe you should also add the “check if wp api is working” in your troubleshooting list by sending a get request to https://abc.com/wp-json/ ??

In apache2.conf, I had this:
<Directory /path-to-wp-directory/>
Options Indexes FollowSymLinks
AllowOverride None
Require all granted
</Directory>

I changed it to this below and it worked.

<Directory /path-to-wp-directory/>
Options Indexes FollowSymLinks
AllowOverride All
Require all granted
</Directory>

I’m going to be purchasing a 1 year license to begin. If we like it, we might purchase the lifetime too.