cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Community Tip - Learn all about PTC Community Badges. Engage with PTC and see how many you can earn! X

Unable to log-in to Mashup from google chrome

Rahul_Raj
9-Granite

Unable to log-in to Mashup from google chrome

Hello everyone,

 

I am facing a quite strange behaviour from Thingworx on Chrome. My customer is unable to log in to the composer from a normal chrome window, whereas she is able to do it from an incognito window. Another customer (in the same corporate network) is redirected to IE when she tries to open the mashup in normal chrome. For both cases, it works just fine from an incognito window. I also work in the same network and I do not face any of these issues. 

 

Any idea why this is happening?

1 ACCEPTED SOLUTION

Accepted Solutions

Apparently it seems like some network issues caused the problem.

ie, the problem persists only when accessed from a certain network.

So, as of now, we can detach (close) this incident from ThingWorx side.

View solution in original post

7 REPLIES 7
PaiChung
22-Sapphire I
(To:Rahul_Raj)

Have you tried emptying the browser cache?

Yes, I tried that, but didn't work.

PaiChung
22-Sapphire I
(To:Rahul_Raj)

Please check the physical logs both the application.log and catalina.log

slangley
23-Emerald II
(To:Rahul_Raj)

Hi @Rahul_Raj.

 

Have you been able to find a solution for this issue?  Do your users experience issues with other browsers?

 

Regards.

 

--Sharon

Not yet. I don't have the acces to the physical logs yet. I will get back to you with more information once I have them. And the problem is only with Google Chrome. Not sure if this happened after a recent routine-update of Chrome.

slangley
23-Emerald II
(To:slangley)

Hi @Rahul_Raj.

 

Just checking to see if you've been able to obtain access to the logs, or has the problem resolved itself?

 

Regards.

 

--Sharon

Apparently it seems like some network issues caused the problem.

ie, the problem persists only when accessed from a certain network.

So, as of now, we can detach (close) this incident from ThingWorx side.

Top Tags