Fixes a misleading "WordPress Cron is disabled" warning introduced by the 2.2.0 remote cron rollout. Users with DISABLE_WP_CRON set (managed hosts, performance setups) will no longer see a false alarm when the remote cron server is handling their checks. Also fixes a broken "Learn how to fix this" link.<\/p>","2.2.0":"
Major improvement: built-in remote cron server (AWS, EU Frankfurt) eliminates the need for external cron services. Reliable monitoring even for low-traffic sites. Auto-registers on activation \u2014 no setup required.<\/p>","2.1.1":"
Fixes Freemius SDK configuration for WordPress.org, adds full i18n support, and resolves a duplicate AJAX call bug.<\/p>","2.1.0":"
Introduces the Pro plan with faster monitoring, SSL checks, and support for up to 100 websites. Free plan continues to work with up to 2 websites and 15-minute intervals. Freemius SDK added for license management.<\/p>","2.0.2":"
Critical fix: monitoring checks now run at the correct interval. Security improvements including XSS and SSRF fixes. Recommended update for all users.<\/p>","2.0.1":"
New Dashboard Widget, improved responsive design, and better cron reliability with atomic locking.<\/p>"},"ratings":{"1":0,"2":0,"3":0,"4":0,"5":2},"assets_icons":{"icon-256x256.png":{"filename":"icon-256x256.png","revision":3496974,"resolution":"256x256","location":"assets","locale":""}},"assets_banners":{"banner-772x250.png":{"filename":"banner-772x250.png","revision":3498236,"resolution":"772x250","location":"assets","locale":""}},"assets_blueprints":{"blueprint.json":{"filename":"blueprint.json","revision":3508874,"resolution":false,"location":"assets","locale":"","contents":"{\"$schema\":\"https:\\\/\\\/playground.wordpress.net\\\/blueprint-schema.json\",\"preferredVersions\":{\"php\":\"8.2\",\"wp\":\"latest\"},\"login\":{\"username\":\"admin\",\"password\":\"password\"},\"landingPage\":\"\\\/wp-admin\\\/admin.php?page=lukstack-uptime-monitor\",\"steps\":[{\"step\":\"installPlugin\",\"options\":{\"activate\":true},\"pluginData\":{\"resource\":\"wordpress.org\\\/plugins\",\"slug\":\"lukstack-uptime-monitor\"}}]}"}},"all_blocks":[],"tagged_versions":["2.0.0","2.0.1","2.0.2","2.1.0","2.1.1","2.2.0","2.2.1"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3461986,"resolution":"1","location":"assets","locale":""},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3461986,"resolution":"2","location":"assets","locale":""},"screenshot-3.png":{"filename":"screenshot-3.png","revision":3461986,"resolution":"3","location":"assets","locale":""},"screenshot-4.png":{"filename":"screenshot-4.png","revision":3461986,"resolution":"4","location":"assets","locale":""},"screenshot-5.png":{"filename":"screenshot-5.png","revision":3461986,"resolution":"5","location":"assets","locale":""}},"screenshots":{"1":"Main dashboard showing all monitored websites with status, response time, and uptime","2":"Adding a new website to monitor","3":"Settings page with webhook configuration","4":"Dashboard widget with quick status overview","5":"Discord notification example","6":"Slack notification example","7":"Help and documentation page"},"jetpack_post_was_ever_published":false},"plugin_section":[],"plugin_tags":[1110,5603,1536,29148,15439],"plugin_category":[54],"plugin_contributors":[255806],"plugin_business_model":[],"class_list":["post-280397","plugin","type-plugin","status-publish","hentry","plugin_tags-alerts","plugin_tags-monitoring","plugin_tags-ssl","plugin_tags-uptime","plugin_tags-webhook","plugin_category-security-and-spam-protection","plugin_contributors-lukmeyer","plugin_committers-lukmeyer"],"banners":{"banner":"https:\/\/ps.w.org\/lukstack-uptime-monitor\/assets\/banner-772x250.png?rev=3498236","banner_2x":false,"banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/lukstack-uptime-monitor\/assets\/icon-256x256.png?rev=3496974","icon_2x":"https:\/\/ps.w.org\/lukstack-uptime-monitor\/assets\/icon-256x256.png?rev=3496974","generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/lukstack-uptime-monitor\/assets\/screenshot-1.png?rev=3461986","caption":"Main dashboard showing all monitored websites with status, response time, and uptime"},{"src":"https:\/\/ps.w.org\/lukstack-uptime-monitor\/assets\/screenshot-2.png?rev=3461986","caption":"Adding a new website to monitor"},{"src":"https:\/\/ps.w.org\/lukstack-uptime-monitor\/assets\/screenshot-3.png?rev=3461986","caption":"Settings page with webhook configuration"},{"src":"https:\/\/ps.w.org\/lukstack-uptime-monitor\/assets\/screenshot-4.png?rev=3461986","caption":"Dashboard widget with quick status overview"},{"src":"https:\/\/ps.w.org\/lukstack-uptime-monitor\/assets\/screenshot-5.png?rev=3461986","caption":"Discord notification example"}],"raw_content":"\n
LukStack Uptime Monitor is a lightweight yet powerful website monitoring solution built for agencies, freelancers, and web professionals who manage multiple websites.<\/p>\n\n
Track uptime, response times, and SSL certificate expiration for all your client sites from a single WordPress dashboard. When something goes wrong, you will know immediately through email notifications or webhook integrations with Slack, Discord, and other services.<\/p>\n\n
Unlike plugins that rely on WordPress Cron (which only runs when someone visits your site), LukStack Uptime Monitor includes a built-in remote cron server<\/strong> operated by the plugin author and hosted on AWS in the EU (Frankfurt) region. Your site is automatically registered on plugin activation and the server triggers your monitoring checks every minute \u2014 reliably, even on low-traffic sites. No personal data is transmitted. No third-party cron services like cron-job.org or UptimeRobot required.<\/p>\n\n LukStack Uptime Monitor automatically formats notifications for popular services:<\/p>\n\n LukStack Uptime Monitor stores the URLs you choose to monitor and their status data. No personal information (admin emails, user accounts, site content) is collected by the plugin itself.<\/p>\n\n The plugin does transmit data to the following external services:<\/p>\n\n All external transmissions are described in detail in the External services section below.<\/p>\n\n This plugin connects to external services as part of its core monitoring functionality. Below is a description of each service, what data is sent, and when.<\/p>\n\n LukStack Uptime Monitor sends HTTP requests to the website URLs you add for monitoring. This is the core functionality of the plugin and is required to check uptime and response times. An SSL connection on port 443 is also made to check the SSL certificate expiration date for HTTPS sites (Pro). These requests are sent automatically by the built-in cron server (see below) and when you manually click \"Check now\". The data sent is a standard HTTP GET request with a custom user agent header. No personal data is transmitted.<\/p>\n\n This plugin connects to the LukStack cron server to ensure reliable monitoring checks even when your WordPress site has no visitors. Because no dedicated privacy policy URL is published for this service, the full data-handling details are documented below.<\/p>\n\n Service operator<\/strong><\/p>\n\n Operated by Luk Meyer (plugin author). Contact: via the WordPress.org support forum for this plugin (https:\/\/wordpress.org\/support\/plugin\/lukstack-uptime-monitor\/).<\/p>\n\n Hosting and location<\/strong><\/p>\n\n Hosted on Amazon Web Services (AWS), region eu-central-1 (Frankfurt, Germany). Data does not leave the EU. The service uses AWS Lambda, AWS DynamoDB, and AWS EventBridge Scheduler. AWS acts as a data processor under a standard data processing agreement.<\/p>\n\n Server endpoint: https:\/\/gt5zheubf8.execute-api.eu-central-1.amazonaws.com<\/p>\n\n What data is transmitted FROM your site TO the cron server<\/strong><\/p>\n\n On plugin activation and when an admin visits the WordPress admin (throttled to at most once per hour):<\/p>\n\n No personal data, no admin email, no user account information, no site content, no visitor data, and no credentials are transmitted.<\/p>\n\n What data is transmitted FROM the cron server TO your site<\/strong><\/p>\n\n Every minute, the cron server sends an HTTP POST request to the REST endpoint \/wp-json\/lukstack\/v1\/trigger on your site, authenticated via the X-LukStack-Secret header. The request body is empty. The sole purpose of this request is to trigger the plugin's internal monitoring logic.<\/p>\n\n What data is stored on the cron server<\/strong><\/p>\n\n No logs of monitored sites, no uptime data, no visitor data, no personal data.<\/p>\n\n Data retention<\/strong><\/p>\n\n Data is kept only as long as the plugin is installed on your site. When the plugin is deleted from your WordPress installation, the site is marked inactive on the cron server after approximately 100 consecutive failed trigger attempts (about 100 minutes) and no further requests are sent. Inactive records may be purged periodically.<\/p>\n\n Your rights and how to exercise them<\/strong><\/p>\n\n You can at any time:<\/p>\n\n Security<\/strong><\/p>\n\n Legal basis (GDPR)<\/strong><\/p>\n\n The processing described above is necessary for the performance of the service you enabled by installing this plugin (Art. 6 (1) (b) GDPR). Only technical identifiers (URL, secret, timestamps) are processed; no special categories of personal data are involved.<\/p>\n\n This plugin uses Freemius SDK for license management, usage tracking (opt-in only), and the upgrade flow. When a user opts in, anonymized data such as the site URL, WordPress version, PHP version, and plugin version may be sent to Freemius servers. Users can opt out at any time.<\/p>\n\n This service is provided by Freemius, Inc.\nTerms of Service: https:\/\/freemius.com\/terms\/\nPrivacy Policy: https:\/\/freemius.com\/privacy\/<\/p>\n\n If you configure a Slack webhook URL in the plugin settings, LukStack Uptime Monitor sends POST requests to the Slack Incoming Webhooks API when a monitored site changes status (goes down, recovers, or has SSL issues). The data sent includes the website URL, its status, response time, and a timestamp. No personal data is transmitted.<\/p>\n\n This service is provided by Slack Technologies, LLC \/ Salesforce, Inc.\nTerms of Service: https:\/\/slack.com\/terms-of-service\nPrivacy Policy: https:\/\/slack.com\/privacy-policy<\/p>\n\n If you configure a Discord webhook URL in the plugin settings, LukStack Uptime Monitor sends POST requests to the Discord Webhooks API when a monitored site changes status. The data sent includes the website URL, its status, response time, and a timestamp. No personal data is transmitted.<\/p>\n\n This service is provided by Discord, Inc.\nTerms of Service: https:\/\/discord.com\/terms\nPrivacy Policy: https:\/\/discord.com\/privacy<\/p>\n\n You may configure any third-party webhook URL (e.g. Microsoft Teams, Zapier, Make, or a custom endpoint). When a monitored site changes status, a POST request with a JSON payload is sent to that URL. The data sent includes the website URL, its status, response time, and a timestamp. No personal data is transmitted. Please refer to the terms of service and privacy policy of the respective service you configure.<\/p>\n\n For support questions, please use the WordPress.org support forum for this plugin.<\/p>\n\n Developed by Luk Meyer.<\/p>\n\n\n The free version supports up to 2 websites. The Pro plan supports up to 100 websites.<\/p><\/dd>\n The free plan checks every 15 minutes. The Pro plan checks every 5 minutes for faster downtime detection.<\/p><\/dd>\n SSL certificate monitoring is available in the Pro plan. You will receive warnings when a certificate is within 30 days of expiring, with critical alerts at 7 days.<\/p><\/dd>\n This can happen if:<\/p>\n\n Try adding your monitoring server IP to any whitelist or firewall rules.<\/p><\/dd>\n No. The monitoring checks run in the background, triggered by the remote cron server every minute (with plan-gated intervals). The actual HTTP checks run asynchronously and do not affect your site frontend performance.<\/p><\/dd>\n Yes. LukStack Uptime Monitor can monitor any publicly accessible website, regardless of the platform.<\/p><\/dd>\n This plugin uses a built-in remote cron server (hosted on AWS, EU Frankfurt) that automatically triggers checks on your site every minute. No setup is required; your site is registered automatically on plugin activation. If checks are not running, verify that:<\/p>\n\n WordPress Cron remains scheduled as a fallback, so checks will also run when visitors hit your site.<\/p><\/dd>\n No. For security reasons, localhost (127.0.0.1) and private IP ranges are blocked from monitoring.<\/p><\/dd>\n The plugin makes outbound requests to:<\/p>\n\n The plugin also receives incoming requests on its REST endpoint (\/wp-json\/lukstack\/v1\/trigger) from the LukStack cron server, authenticated by a shared secret. See the External services section for full details.<\/p><\/dd>\n\n<\/dl>\n\n\nFree Plan Features<\/h4>\n\n
\n
Pro Plan Features<\/h4>\n\n
\n
Who Is This For?<\/h4>\n\n
\n
How It Works<\/h4>\n\n
\n
Webhook Integrations<\/h4>\n\n
\n
Privacy<\/h4>\n\n
\n
External services<\/h3>\n\n
Monitored Websites<\/h4>\n\n
LukStack Cron Server<\/h4>\n\n
\n
\n
\n
\n
Freemius<\/h4>\n\n
Slack (optional)<\/h4>\n\n
Discord (optional)<\/h4>\n\n
Generic Webhooks (optional)<\/h4>\n\n
Additional Information<\/h3>\n\n
Requirements<\/h4>\n\n
\n
Support<\/h4>\n\n
Credits<\/h4>\n\n
Automatic Installation<\/h4>\n\n
\n
Manual Installation<\/h4>\n\n
\n
After Activation<\/h4>\n\n
\n
\n
How many websites can I monitor?<\/h3><\/dt>\n
How often are websites checked?<\/h3><\/dt>\n
Can I monitor SSL certificates?<\/h3><\/dt>\n
Why does my site show as DOWN when it is actually online?<\/h3><\/dt>\n
\n
Will this slow down my WordPress site?<\/h3><\/dt>\n
Can I monitor non-WordPress sites?<\/h3><\/dt>\n
How do I set up Slack notifications?<\/h3><\/dt>\n
\n
How do I set up Discord notifications?<\/h3><\/dt>\n
\n
Why are automatic checks not running?<\/h3><\/dt>\n
\n
LukStack-Cron-Runner<\/code><\/li>\nCan I monitor localhost or internal sites?<\/h3><\/dt>\n
Does this plugin send any data externally?<\/h3><\/dt>\n
\n
2.2.1<\/h4>\n\n
\n
2.2.0<\/h4>\n\n
\n
2.1.1<\/h4>\n\n
\n
2.1.0<\/h4>\n\n
\n
2.0.2<\/h4>\n\n
\n
2.0.1<\/h4>\n\n
\n
2.0.0<\/h4>\n\n
\n