Is anyone seeing 'Not Secure' in the browser on CrazyEngineers pages?

@thebigk • Oct 26, 2024

Oct 26, 2024

1.4K

Could you please browse 2-3 pages on CrazyEngineers and let us know if you encountered 'Not Secure' notification in the browser? Your feedback would help us fix issues. Thank you in advance.

Like 0 Replies 7

Replies

Welcome, guest

Join CrazyEngineers to reply, ask questions, and participate in conversations.

CrazyEngineers powered by Jatra Community Platform

Ramani Aswath

@ramani-VR4O43 • Jul 27, 2018

Firefox locked me out of CE a few minutes back saying site insecure. Seems temporary as I am back now.

0
Kaustubh Katdare

@thebigk • Jul 27, 2018

Yes, there was an issue a couple of minutes ago and it's been fixed. Just want to make sure that people from different locations are seeing secure pages.
We need more responses here.

0
Anoop Kumar

@anoop-SlERLg • Jul 27, 2018

No issues for me.
Browser: Chrome Desktop V 67.0.3396.62

0
saandeep sreerambatla

@saandeep-MxxXlX • Jul 28, 2018

Navigated through multiple pages dont see any message.

0
Ankita Katdare

@abrakadabra • Jul 29, 2018

I think you all need to check once from your mobile browsers. #-Link-Snipped-# #-Link-Snipped-# #-Link-Snipped-# sir The problem might occur when you use mobile data. Please check once and let us know if you face any issues.

0
Ramani Aswath

@ramani-VR4O43 • Jul 29, 2018

I rarely use the phone for anything other than making or receiving calls. If at all I do go to the browser CE is on screen. I did not face any problem using it. Tried just now. Working well.

0
Kaustubh Katdare

@thebigk • Jul 29, 2018

Update:
We found out that this error appears only when the user omits the 'www' part from the URL, and is using FireFox or Safari or MI browser.Â
Chrome, however correctly appends the 'www' part to the URL even when the user did not mention it.Â
We'll have to work out a solution for this to work on all types of browsers.Â
---Â
Special thanks toÂ #-Link-Snipped-# for bringing this to our attention. He helped identify a notorious issue in our configuration that we couldn't have identified otherwise. I think lot of people who were typing the site's address directly in the browser were getting this issue and couldn't figure out why the site wasn't working.Â
Thank you once, again!

0