Title: Events Calendar Missing API endpoint /html
Last modified: February 17, 2026

---

# Events Calendar Missing API endpoint /html

 *  Resolved [TeamITS](https://wordpress.org/support/users/teamits/)
 * (@teamits)
 * [3 months, 3 weeks ago](https://wordpress.org/support/topic/missing-api-endpoint/)
 * At some point after migrating a site we discovered changing pages in Event Calendar
   doesn’t work.
 * example.com/wp-json works in a browser.
 * example.com/wp-json/tribe/views/v2 works. Other endpoints work.
 * example.com/wp-json/tribe/views/v2/html logs an error like “…[error] 3916993#
   0: *3616844 openat() “/var/www/vhosts/example.com/httpdocs/wp-json/tribe/views/
   v2/html” failed (2: No such file or directory)…” in proxy_error_log on Plesk.
   At this point the site shows an empty page (header and footer only).
 * If I type in the example.com/httpdocs/wp-json/tribe/views/v2/html URL the browser
   redirects to the site home page.
 * If we open the < or > or other links on a calendar page in a new tab the page
   opens and displays correctly.
 * Any ideas on why /html is not found?
    -  This topic was modified 3 months, 3 weeks ago by [TeamITS](https://wordpress.org/support/users/teamits/).

Viewing 12 replies - 1 through 12 (of 12 total)

 *  Plugin Support [tristan083](https://wordpress.org/support/users/tristan083/)
 * (@tristan083)
 * [3 months, 3 weeks ago](https://wordpress.org/support/topic/missing-api-endpoint/#post-18825552)
 * Hi [@teamits](https://wordpress.org/support/users/teamits/) ,
 * Thank you for reaching out.
 * This can be due to outdated permalinks database or caching and performance solutions
   so I recommend starting with those:
    - Regenerate the site’s permalinks (see [How to Regenerate Your Permalinks in WordPress](https://www.wpbeginner.com/beginners-guide/how-to-regenerate-your-permalinks-in-wordpress/))
      and ensure that the Post name structure is set.
    - Flush your site’s cache and configure exclusions per our [Caching with The Events Calendar](https://theeventscalendar.com/knowledgebase/guide/caching-with-the-events-calendar/)
      guide.
 *  Thread Starter [TeamITS](https://wordpress.org/support/users/teamits/)
 * (@teamits)
 * [3 months, 3 weeks ago](https://wordpress.org/support/topic/missing-api-endpoint/#post-18826525)
 * Thanks for the reply. We had regenerated permalinks; I did it again to no avail.
   We had changed from Post to something else, and back again.
 * We have no cache plugins installed. The closest this site comes is it has a “
   expires 30d;” tag that would apply to .css files.
 * “Enable the Month View Cache” is unchecked.
 *  Plugin Support [Darian](https://wordpress.org/support/users/d0153/)
 * (@d0153)
 * [3 months, 3 weeks ago](https://wordpress.org/support/topic/missing-api-endpoint/#post-18827479)
 * Hi there,
 * Thank you for your response. To assist you better, could you please provide the
   URL of your website so we can take a closer look? This will help us investigate
   the issue further.
 *  Thread Starter [TeamITS](https://wordpress.org/support/users/teamits/)
 * (@teamits)
 * [3 months, 3 weeks ago](https://wordpress.org/support/topic/missing-api-endpoint/#post-18827673)
 * sure, it is hinsdale.church/events
 * (also the “expires” tag would apply to various image files, just not .js)
 * Also as I reread my OP, I need to correct something…the error is logged when 
   trying to click links in the calendar/event listing. The /html URL redirects 
   to the site home page because it’s 404, as I wrote.
 *  Plugin Support [Darian](https://wordpress.org/support/users/d0153/)
 * (@d0153)
 * [3 months, 3 weeks ago](https://wordpress.org/support/topic/missing-api-endpoint/#post-18828478)
 * Hi [@teamits](https://wordpress.org/support/users/teamits/)
 * Thanks for your response.
 * After checking, it looks like there may be a conflict on your site. To help isolate
   the cause, could you please try activating **only our plugins** along with a 
   default theme such as **Twenty Twenty One**, then check if the issue still occurs?
 * If the issue is resolved, please reactivate your plugins and theme **one at a
   time**, testing after each step, to identify which one may be causing the conflict.
 * This should help narrow things down, and we can take it from there.
 * As always, please make sure to run these tests on a **staging version** of your
   live site to avoid impacting production.
 * You can follow this guide from **The Events Calendar** on how to set one up:
   
   [https://theeventscalendar.com/knowledgebase/how-to-set-up-a-staging-site-for-your-wordpress-website/](https://theeventscalendar.com/knowledgebase/how-to-set-up-a-staging-site-for-your-wordpress-website/)
 *  Thread Starter [TeamITS](https://wordpress.org/support/users/teamits/)
 * (@teamits)
 * [3 months, 3 weeks ago](https://wordpress.org/support/topic/missing-api-endpoint/#post-18828543)
 * The main person working on this site has been out a couple days. Will try to 
   test further.
 * Previously I’m told he did try disabling plugins and a default theme, as per 
   your site, to no avail. However using a _preview_ in WordPress of another theme
   works fine, for the links on the event/calendar page.
 *  Plugin Support [tristan083](https://wordpress.org/support/users/tristan083/)
 * (@tristan083)
 * [3 months, 2 weeks ago](https://wordpress.org/support/topic/missing-api-endpoint/#post-18829066)
 * Hi [@teamits](https://wordpress.org/support/users/teamits/) ,
 * Thank you for your message and the update.
 * Please feel free to let us know how things go or if you have further questions/
   concerns.
 *  Plugin Support [Darian](https://wordpress.org/support/users/d0153/)
 * (@d0153)
 * [3 months, 2 weeks ago](https://wordpress.org/support/topic/missing-api-endpoint/#post-18832441)
 * It looks like this thread has become inactive, so I’ll go ahead and close it 
   for now.
 * Please feel free to reopen this thread or start a new one if you have any further
   questions or concerns—we’re always happy to help.
 *  Thread Starter [TeamITS](https://wordpress.org/support/users/teamits/)
 * (@teamits)
 * [3 months, 2 weeks ago](https://wordpress.org/support/topic/missing-api-endpoint/#post-18832831)
 * Hi, he did verify today that what I wrote above was correct, that it didn’t work
   with plugins disabled and a WP theme.
 *  Plugin Support [Darian](https://wordpress.org/support/users/d0153/)
 * (@d0153)
 * [3 months, 2 weeks ago](https://wordpress.org/support/topic/missing-api-endpoint/#post-18833557)
 * Thanks for your response.
 * > However using a _preview_ in WordPress of another theme works fine, for the
   > links on the event/calendar page.
 * Were you able to try activating the said theme and see if it actually resolves
   the issue? If so, then the issue might be coming from your theme that is in conflict
   with our plugin.
 * I took a closer look at the issue further, and I can confirm what’s happening.
 * When the AJAX request is sent to the following REST endpoint:
 * `/wp-json/tribe/views/v2/html`
 * the server responds with a **301 redirect** and forwards the request to the site’s
   homepage instead. Because of this redirect, the request never reaches the REST
   API, which causes the AJAX call to fail.
 * REST API and AJAX requests are expected to return a **200 response**. Redirects—
   especially 301s—will break these requests and prevent features like Past Events
   navigation, pagination, or filtering from working correctly.
 * This behavior is typically caused by a redirect rule or configuration on the 
   site, such as:
    - A forced canonical redirect from an SEO plugin
    - HTTP → HTTPS or domain normalization rules
    - A security or firewall plugin blocking REST requests
    - Server-level redirects in `.htaccess`, Nginx, or Cloudflare
 * To resolve this, please ensure that any redirect rules explicitly **exclude REST
   API requests**, particularly:
 * `/wp-json/*`
 * As a quick test, you can try temporarily disabling SEO, security, or caching 
   plugins to identify whether one of them is triggering the redirect. Additionally,
   accessing the REST endpoint directly in a browser should return JSON—if it redirects
   instead, that confirms the issue is happening before WordPress can process the
   request.
 * Once the redirect is removed or adjusted to allow REST API requests, the AJAX
   functionality should work as expected. Let me know how it goes.
 *  Thread Starter [TeamITS](https://wordpress.org/support/users/teamits/)
 * (@teamits)
 * [3 months, 2 weeks ago](https://wordpress.org/support/topic/missing-api-endpoint/#post-18833869)
 * Any idea why it works if we open the link in a new tab/window?
 * Will triple check but we had disabled Plesk security and other plugins to test,
   previously.
 *  Plugin Support [Darian](https://wordpress.org/support/users/d0153/)
 * (@d0153)
 * [3 months, 2 weeks ago](https://wordpress.org/support/topic/missing-api-endpoint/#post-18835006)
 * This is because the calendar layout is loaded during the initial page load rather
   than via an AJAX request.
 * Please feel free to let us know how it goes or if you have any further questions
   or concerns.

Viewing 12 replies - 1 through 12 (of 12 total)

You must be [logged in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fmissing-api-endpoint%2F%3Foutput_format%3Dmd&locale=en_US)
to reply to this topic.

 * ![](https://ps.w.org/the-events-calendar/assets/icon-256x256.gif?rev=2516440)
 * [The Events Calendar](https://wordpress.org/plugins/the-events-calendar/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/the-events-calendar/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/the-events-calendar/)
 * [Active Topics](https://wordpress.org/support/plugin/the-events-calendar/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/the-events-calendar/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/the-events-calendar/reviews/)

 * 12 replies
 * 3 participants
 * Last reply from: [Darian](https://wordpress.org/support/users/d0153/)
 * Last activity: [3 months, 2 weeks ago](https://wordpress.org/support/topic/missing-api-endpoint/#post-18835006)
 * Status: resolved