NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
simbla
Oct 14, 2024Follower
canvas offline since sept 11 2024
Sounds like lots of people having problems with their Meural saying Offline. Netgear tech support have thus far been less than useful, asking me to do all the things I have already tried (lots of times). I currently have a case open with them, but not getting any traction at all with the nice Phillipino? guy called Wendy who is trying to help. He actually got a bit rude at one point so I had to ask him to soften his tone with me. He thought he was clever by asking me how my network topology was layed out and getting shirty with me. Oh please.
I have found some issue with the SSL cert for amqp.meural.com, which is an address which my meural attempts to contact before going "OFFLINE"....
some info for fun..
Canvas Software Version 2.0.9
Web App Version v4.4.11
Last Sync 2024-09-11
I have packet sniffed my Meural and it appears to be saying there is a SSL cert issue. Which is proven by browsing to these addresses :
Sure enough, if I visit https://99.80.99.6 (or https://amqp.meural.com) - the SSL cert appears expired.
See attached pics
here is the result of a quick packet sniff on the meural (10.0.0.200). A fatal error is enough to stop anyone connecting to their amqp message queue.
Further looking shows that api.meural.com uses a nice wildcard SSL certificate - which could also be used for amqp.meural.com - if the engineers decided to move that SSL cert to the other web front end for amqp...
please take note any engineers with Netgear - this may help to get everyones Meural working again ??
It could be that the SSL cert from my Meural is expired, as the packet sniff shows the bad TLS 1.2 packet to be going from my Meural, back to amqp.meural.com's server..
I dont know.. I just want a working Meural.
thanks
1 Reply
Replies have been turned off for this discussion
- FURRYe38Guru - Experienced User
Not much else can be done. All in NGs hands currently. You'll need to keep in contact with NG support and be patient while NG gets this figured out.