Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't disable monitor if jetpack site is offline #34022

Open
gravityrail opened this issue Jun 16, 2019 · 2 comments
Open

Can't disable monitor if jetpack site is offline #34022

gravityrail opened this issue Jun 16, 2019 · 2 comments

Comments

@gravityrail
Copy link
Contributor

I have a development site that runs on my laptop and is frequently offline. I decided to disable monitor so that I don't keep getting notifications when I close my laptop. Trying to change this setting while the site was offline was impossible. Seems to me that disabling monitor for sites which are offline a lot or entirely would be a common use case. Otherwise people have no choice than to bring the site back online in order to disable the offline notifications.

Steps to reproduce

  1. Starting at URL: https://wordpress.com/settings/security/goldsounds.ngrok.io
  2. Click to disable monitor
  3. Get message "something went wrong"

What I expected

What happened instead

Browser / OS version

Screenshot / Video

https://drive.google.com/file/d/1-3lwqh_L8Zk4iY38Num1yArPPjMQMXMi/view?usp=drivesdk

Context / Source

@stale
Copy link

stale bot commented Dec 25, 2020

This issue has been marked as stale and will be closed in seven days. This happened because:

  • It has been inactive in the past 9 months.
  • It isn't a project or a milestone, and hasn’t been labeled `[Pri] Blocker`, `[Pri] High`, `[Status] Keep Open`, or `OSS Citizen`.

You can keep the issue open by adding a comment. If you do, please provide additional context and explain why you’d like it to remain open. You can also close the issue yourself — if you do, please add a brief explanation.

@github-actions
Copy link

This issue is stale because it has been 180 days with no activity. You can keep the issue open by adding a comment. If you do, please provide additional context and explain why you’d like it to remain open. You can also close the issue yourself — if you do, please add a brief explanation and apply one of relevant issue close labels.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants