Public views requires login

When accessing public charts via link it shows message that i was logged out and wants me to login. I am using it with users which dont have mathworks account. Is this any new feature or Bug?

[Christopher Stapels]

Can you paste a sample link?

I faintly recall seeing something like this before but not being able to verify it again. It could be a cookie issue, you might try clearing mathworks and thingspeak cookies on the target machine.

[Nikita Lesko]

https://thingspeak.com/channels/66456

[Nikita Lesko]

Clearing cookies have not made situation different.

[Christopher Stapels]

Thanks for giving the cookies a try. I can access that link with no issue on two different machines that are logged in, but not in incognito mode. Ill report it as a bug and see if others here can reproduce it.

[Don Hill]

I noticed the same behavior yesterday with my channel. I just tried now to access Nikita's channel. On my laptop and my wife's laptop (both windows 10, Firefox 125.0.2) the page loads fast but immediately switches to the loggin page. I also have a very old desktop running Linux (Raspbian, Firefox 78.15.0esr 32 bit)) and it does load Nikita's page and stays there (works fine with my channel too). It loads very slowly as does everything with that old computer. I then deleted all cookies, cache, browsing history and offline website data on my laptop, but that did not change the behavior, page loads and immediatly goes to log in page.

[Pierre]

I have the same problem too...

[Christopher Stapels]

Thank you for reporting. We are actively working on this issue.

[Don Hill]

For what it is worth, maybe help with your troubleshooting. I bought a new (old used) computer today. The ancient desktop will be retired, and the new (old used) computer is actually faster than my laptop. So I opened my Thinkspeak page and thought, hey - they fixed it. Refreshed the page and same problems, loads fast and immediately goes to log in page. So it must be something to do with cookies, browser cache etc, even though clearing those did not fix it. ????? The ancient computer will still load the page and stay there. Baffling.

[Christopher Stapels]

This is good information, it may mean it is releated to a browser update. Can you tell us what browser and version you are using on the ancient computer?

[Nikita Lesko]

to me it is not working in Opera 108.0.5067.29 on windows 10 and also on Android google chrome and also in android opera.

[Christopher Stapels]

Thanks @Nikita Lesko we will keep looking into it.

[Don Hill]

Christopher, maybe you missed it in the first post, the ancient computer is running the Raspian operating system (intended for the Raspberry Pi) and Firefox 78.15.0esr 32 bit. And woouldn't you know it, this morning it is also going to the log in page after opening the public view. But doing it so slowly that all the graphs can be read.

I have a couple linux distros on USB sticks. I will play with those and see if I can discover anything.

[Christopher Stapels]

@Don Hill Thanks - switching between too many threads...I appreciate your work and info on this.

[Don Hill]

Following the logic that it might be a browser update issue, I installed Firefox 115.10.0 esr (64bit) and that didn't work. So I re-installed 125.0.2 (which doesn't work).

I opened chrome 123.0.6312.106 and while it was busy downloading an update, I opened my thingspeak page with no problems. Once the download was finished and I installed chrome 124.0.6367.92 - then the same problem with going to the log in page. I can't think of anything else to try.

Answer 1

[Christopher Stapels]

Thanks for reporting this issue. We have a fix in progress, but in the meantime please try the following workaround: Go to the thingspeak homepage and click the thingspeak icon in the upper left. Then try to visit a public page again without logging in.

[Jose Maria Borgatello]

Hello Christopher, if you are right, that solves the problem during that session of opening the browser, but if the browser is closed and opened again, the problem appears again.

Thanks for working on solving the problem.

[Christopher Stapels]

We have released an update to remove this problem. Please refresh your browser and let us know if you continue to see the issue.