I can't login to some web sites

edoelas · 2018-05-02 15:39:27

I'm having an strange problem: I can't login in some web pages.
I think that this problem is due to the OS because I have tried to login using the same browsers (firefox and chrome) from windows and everything worked fine.
Some sites I can't login are:
- https://flow-e.com/workflow
- https://www.unrealengine.com/en-US/what … l-engine-4

Im not sure which information I should provide in roder to be helped but there is a better description of my situation:

Useful information:
- I can login in other websites as facebook or youtube fine using the same email
- It does not say that there is a problem with my information, simply everything seems to work fine but when I get redirected to the main page I'm not logged.
- In the unreal engine web page I can see how it shows during a fraction of a second the message "Signin you out..."
- ifconfig wlp3s0 shows (I'm using this interface):

wlp3s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.129  netmask 255.255.255.0  broadcast 192.168.1.255
        inet6 fe80::b210:41ff:fefa:4ba5  prefixlen 64  scopeid 0x20<link>
        ether b0:10:41:fa:4b:a5  txqueuelen 1000  (Ethernet)
        RX packets 153599  bytes 203929808 (194.4 MiB)
        RX errors 0  dropped 0  overruns 0  frame 55863
        TX packets 93585  bytes 9783689 (9.3 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 19

Already tried:
- Use different browsers (firefox and chrome)
- Clean browsing data
- Clean cookies
- Using private window

Thanks!

Last edited by edoelas (2018-05-02 16:48:10)

loqs · 2018-05-02 17:32:50

In firefox Ctrl + Shift + e for the network panel then try logging into one of the affected sites compare the Request Headers and Response Headers.
User-Agent will be different but there may be other differences.

edoelas · 2018-05-02 21:32:56

loqs wrote:

In firefox Ctrl + Shift + e for the network panel then try logging into one of the affected sites compare the Request Headers and Response Headers.
User-Agent will be different but there may be other differences.

Im not sure which are the steps that I must execute in order to solve my problem following your advice. I know that from the network panel what I see are the packages, but I don't know what I should compare and why. If you address me a guide in order to understand how to do it I would appreciate it.

Last edited by edoelas (2018-05-02 21:34:05)

loqs · 2018-05-02 21:39:37

With the network panel open make a request all the new requests should be listed in the network panel.
Select one and a new panel on the right should appear with the headers tab selected.
In the new panel below Filter Headers should be Response Headers and below that Request Headers those are what I was suggesting you compare.

edoelas · 2018-05-03 21:42:44

Okay, for example, in one package I can found:
Response headers (342 B)
Access-Control-Allow-Credentials: true
Access-Control-Allow-Origin: https://identity.flow-e.com
Access-Control-Expose-Headers: X-Results-Data-Source
Connection: keep-alive
Content-Type: text/plain
Date : Thu, 03 May 2018 20:57:42 GMT
Timing-Allow-Origin: *
X-Request-Id: 3111f7bd-7c4d-4259-b06a-a2104a05d723

Request headers (394 B)
Accept: */*
Accept-Encoding: gzip, deflate, br
Accept-Language: en-US,en;q=0.5
Connection: keep-alive
Content-Length: 526
Content-Type: text/plain;charset=UTF-8
Host : logx.optimizely.com
Origin: https://identity.flow-e.com
Referer: https://identity.flow-e.com/account/signup
User-Agent: Mozilla/5.0 (X11; Linux x86_64…) Gecko/20100101 Firefox/59.0

If I compare them I can see that most of the "attributes" (I'm not sure how they are called) names are different and the ones that are equals have pretty similar information. Is there any specific "attribute" that I have to look for?

I also have found that some packages does not have the typical 200 status code and have 302 (Found) and 304 (not modified). Does this have any importance?

Thanks!

seth · 2018-05-03 21:54:25

I think the idea was to compare the package headers on a working session (windows) and a broken one.
The should initially match and at some point deviate. That point is the critical region.

For a random try: install an extension that allows you to spoof the useragent and use a user agent from a windows browser - a stupid useragent switch might default to logout with "unknown" browsers.

Arch Linux

#1 2018-05-02 15:39:27

I can't login to some web sites

#2 2018-05-02 17:32:50

Re: I can't login to some web sites

#3 2018-05-02 21:32:56

Re: I can't login to some web sites

#4 2018-05-02 21:39:37

Re: I can't login to some web sites

#5 2018-05-03 21:42:44

Re: I can't login to some web sites

#6 2018-05-03 21:54:25

Re: I can't login to some web sites

Board footer