Jump to content

ryanlester

Members
  • Posts

    10
  • Joined

  • Last visited

Reputation

0 Neutral
  1. Great, thanks again for the help!
  2. Thanks, appreciate you taking care of that so quickly! Also, sorry to bug you again, but would you be able to whitelist chat.doctor2.doctor as well? (That's definitely the last one for now; I'd forgotten earlier that it was a separate domain from account.doctor2.doctor.)
  3. Got it, thanks for clarifying that. In that case, I'll limit my request to account.doctor2.doctor (which is the only one that's an active blocker at the moment), and hopefully we can get this sorted on our end sooner rather than later.
  4. Actually, sorry, while we're at it I'll just give you an exhaustive list of the domains we'd ultimately want to whitelist for the same reason (I guess I can't edit that comment?): burner.cyph.app www.burner.cyph.app cyph.audio www.cyph.audio cyph.download www.cyph.download cyph.im www.cyph.im cyph.io www.cyph.io cyph.me www.cyph.me cyph.video www.cyph.video cyph.ws www.cyph.ws account.doctor2.doctor www.account.doctor2.doctor audio.cyph.healthcare www.audio.cyph.healthcare beta-staging.cyph.app www.beta-staging.cyph.app beta.cyph.app www.beta.cyph.app chat.cyph.healthcare www.chat.cyph.healthcare chat.doctor2.doctor www.chat.doctor2.doctor chctelehealth.pki.ws www.chctelehealth.pki.ws cyph.app www.cyph.app cyph.healthcare www.cyph.healthcare cyph.me www.cyph.me cyph.pro www.cyph.pro cyph.ws www.cyph.ws debug.cyph.app www.debug.cyph.app inova.cyph.healthcare www.inova.cyph.healthcare lvkci.cyph.ws www.lvkci.cyph.ws master.cyph.app www.master.cyph.app medical.cyph.pro www.medical.cyph.pro staging.account.doctor2.doctor www.staging.account.doctor2.doctor staging.audio.cyph.healthcare www.staging.audio.cyph.healthcare staging.chat.cyph.healthcare www.staging.chat.cyph.healthcare staging.chat.doctor2.doctor www.staging.chat.doctor2.doctor staging.chctelehealth.pki.ws www.staging.chctelehealth.pki.ws staging.cyph.app www.staging.cyph.app staging.cyph.healthcare www.staging.cyph.healthcare staging.cyph.me www.staging.cyph.me staging.cyph.pro www.staging.cyph.pro staging.inova.cyph.healthcare www.staging.inova.cyph.healthcare staging.lvkci.cyph.ws www.staging.lvkci.cyph.ws staging.medical.cyph.pro www.staging.medical.cyph.pro staging.starfleet.cyph.ws www.staging.starfleet.cyph.ws staging.video.cyph.healthcare www.staging.video.cyph.healthcare staging.wote.cyph.ws www.staging.wote.cyph.ws starfleet.cyph.ws www.starfleet.cyph.ws video.cyph.healthcare www.video.cyph.healthcare wote.cyph.ws www.wote.cyph.ws
  5. Thanks again for your help earlier. We're still planning to investigate a more permanent solution, but in the meantime would you be able to whitelist the following domains as well? account.doctor2.doctor audio.cyph.healthcare chat.cyph.healthcare chat.doctor2.doctor chctelehealth.pki.ws cyph.healthcare cyph.pro inova.cyph.healthcare lvkci.cyph.ws medical.cyph.pro starfleet.cyph.ws video.cyph.healthcare wote.cyph.ws
  6. Ah, got it, so it's not the use of persistent storage (followed by a login form) in and of itself, but that specific rapid fire behavior. I'll make a note for us to look more into that and whether it's possible for us to address, thanks!
  7. Perfect, thanks @gonzo! Unfortunately, the use of persistent storage is a necessary part of the WebSign runtime, not related to the Cyph application itself or the login form in particular. We can and may remove the immediate notification permission request, but there isn't much we can do about the storage request.
  8. Awesome, thanks! I'd still like to get a permanent solution in place, as noted initially, but I really appreciate you guys being able to address the immediate issue so quickly.
  9. Good to know, thanks for clarifying that! If the issue is that simple, it may be possible for us to resolve on our end. (To clarify my comment on whitelisting, I was referring to the Malwarebytes whitelist, not something I would want our users to have to do on their end.) That being said, we don't fire any alerts, at least not during the initial load of the application, and definitely not in quick succession. Could this be caused by browser permission prompts instead? We do request access to the Storage API and Notifications, both of which can result in user-facing prompts.
  10. A couple of our customers recently report having our application at https://cyph.app blocked by Malwarebytes. It's possible that what Cyph is doing under the hood may be triggering some heuristic on MB's end, for example its use of IPFS via third-party gateway servers or other low-level details of WebSign (https://www.cyph.com/websign). It's critical that the underlying root cause be addressed, because we white label Cyph for some customers to run on custom domains. However, as a quick fix, simply whitelisting cyph.app would also be acceptable.
Back to top
×
×
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.