[Dsnuts]

You guys rock. Everything works as it should. Appreciate you guys.

 

[MrWalkman]

It seems that likes are no longer visible in private messages. It's not somethinf important, but they wee visible before.

I'm accessing Head-Fi from my smartphone (1080p resolution).

 

[joe]

Are you in portrait or landscape orientation?

 

[MrWalkman]

I checked it in the landscape orientation and it's the same thing.

I also just checked now on Google Chrome on PC, and it's the same situation.

Feel free to send me a PM and I can like the message so you can confirm it - or maybe you already have a PM with a message of yours which is liked by someone.

For posts it works fine, I can see messages and who liked them.

 

[joe]

Thanks for the report, @MrWalkman . When I read your post earlier this morning, I thought you meant the one in the Upper right of a post. (My bad.) We'll investigate this. Thanks again.

 

[joe]

It seems that likes are no longer visible in private messages. It's not somethinf important, but they wee visible before.

I'm accessing Head-Fi from my smartphone (1080p resolution).

This should be fixed now. Thanks to @warrenpchi for the fix!

 

[MrWalkman]

This should be fixed now. Thanks to @warrenpchi for the fix!

It works indeed. Thanks to everyone involved for getting this fixed!

 

[SoundBytes]

We are not blocking any ISPs. Sounds like you'll want to contact your provider to see what's going on.


If you're referring to the font color in the login text fields, we're working on changing that to something that can be read easily.

Ok,
Safari 2021, for some reason cannot see the "Like" on forums to like posts. I can open Firefox and other browsers no problems. Just wondering why I can see everything except the "Like" options on posts. Not sure if anyone is experiencing this or if there is an adjustment I need to make.

Nevermind. Right click on extension, select manage extensions, uncheck block social widgets. Thanks for indulging me all. Listen on!

Thanks

 

[warrenpchi]

You're welcome!

 

[RCBinTN]

This may be my fault (cleared all my browsing data) but I can't get a secure connection to Head-Fi. The error is that your certificate is not valid. See the screen shots. I'm on a MacBook Pro running OSX 10.11.6 El Capitan. Thanks for any ideas!

 

[MrWalkman]

This may be my fault (cleared all my browsing data) but I can't get a secure connection to Head-Fi. The error is that your certificate is not valid. See the screen shots. I'm on a MacBook Pro running OSX 10.11.6 El Capitan. Thanks for any ideas!

You could check your MacBook's time and date, having the wrong date set can cause this as well.

 

[RCBinTN]

Thanks. I tried that first, and it's accurate.

 

[joe]

Hi @RCBinTN !

Okay, so it appears it's an issue with the issuing authority, because our certificate IS valid (You can see by the date that it is still valid -- I watch that thing like a bloody hawk, I tell ya.) Here's how you can correct it, since it looks like you're using Chrome. (I just did this myself while investigating.)

1. Click the lock in the address bar.
2. Click "Site Settings".
3. Click "Clear Data".

This will log you out, but if you restart your browser, you'll have the correct certificate showing. Just sign back in and you're good to go. (Thanks to @HF_Ryan for giving me the fix, to give you the fix.)

 

[HF_Ryan]

This may be my fault (cleared all my browsing data) but I can't get a secure connection to Head-Fi. The error is that your certificate is not valid. See the screen shots. I'm on a MacBook Pro running OSX 10.11.6 El Capitan. Thanks for any ideas!

Hi @RCBinTN,

It looks like you have the correct certificate for Head-Fi, but have an out of date certificate for our issuing authority (R3). You should be able to resolve this by clearing your local site data for Head-Fi. It appears that you're using Chrome (or another Chromium-based browser), so clearing site data is a simple process. First, click the SSL area of the address bar (currently reading "Not secure") and then click "Site settings". This will bring up a new tab that will have a "Clear data" button near the top right. Go ahead and clear the data. Since you'll no longer have a copy of the certificate, your browser will be forced to download the full chain, including the latest certificate from R3. You'll need to log back into Head-Fi afterwards, but the SSL situation should be resolved.

Please let me know if this resolved your issue.

Best,
Ryan

 

[HF_Ryan]

Hi @RCBinTN !

Okay, so it appears it's an issue with the issuing authority, because our certificate IS valid (You can see by the date that it is still valid -- I watch that thing like a bloody hawk, I tell ya.) Here's how you can correct it, since it looks like you're using Chrome. (I just did this myself while investigating.)

1. Click the lock in the address bar.
2. Click "Site Settings".
3. Click "Clear Data".

This will log you out, but if you restart your browser, you'll have the correct certificate showing. Just sign back in and you're good to go. (Thanks to @HF_Ryan for giving me the fix, to give you the fix.)

Looks like @joe beat me to the punch!

I'll just go back to hiding in my dev cave...