Can't log in to bug reporting system (Trac)
#1
"Missing or invalid form token. Do you have cookies enabled?"
Refuses to let me log in, so I can't report a bug.

Anyone else having this? Quite frustrating.
Same username.
Reply
#2
Have the same issue.
Image
Reply
#3
I think someone said that it can be fixed if you delete the browser cookie for Trac.
Reply
#4
I have that same problem in my firefox browser. Works in IE 11.

scott s.
.
Reply
#5
If you use Chrome try Incognito mode.
Reply
#6
Have deleted cookies, but still not working in Firefox.
Refuse to use IE out of principle!

Oh well the bug wanted to work on has been sitting untouched for 15 months, what's another week....
Reply
#7
Or use Private Window in Firefox.

It looks like notifications are still broken, so other means of communication needed too or likely to have Trac posts go even more unheeded than usual.
Reply
#8
Threadjacking a little (sorry) - I've not been able to connect to trac.kodi.tv whenever I've tried recently - I get a 403/forbidden on /, and a 404/not found on, say, /reports.

Just me?
Reply
#9
EDIT

Interesting... nslookup suggests that I default to

Code:
$ nslookup trac.kodi.tv
Server:    127.0.1.1
Address:    127.0.1.1#53

Non-authoritative answer:
Name:    trac.kodi.tv
Address: 205.251.128.242

... and that fails. However, bring up a US VPN, and I get:

Code:
$ nslookup trac.kodi.tv
Server:    127.0.1.1
Address:    127.0.1.1#53

Non-authoritative answer:
Name:    trac.kodi.tv
Address: 46.43.42.37

... and that works.

Dropping the VPN and going straight to 46.43.42.37, and I can access the site once again...
Reply
#10
(2016-04-06, 16:36)Prof Yaffle Wrote: Dropping the VPN and going straight to 46.43.42.37, and I can access the site once again...

I confirm that using this IP address rather than http://trac.kodi.tv/ works. I can log on, view tickets, etc.

Perhaps this is a DNS issue?
Reply
#11
No, not DNS - the nslookup would fail then, and a direct connection to http://205.251.128.242 would work, which it doesn't.

It's also unlikely to be ISP peering, as I would have thought that a VPN connection would defeat that - but, again, looping through a US breakout and then back to the 205.251.128.242 address also fails.

Most likely would be a need for login credentials, a lack of readable index.htm (or similar), or no read permission to the http daemon to the html files would be my guess. All are odd if it's mirrored, so it is possible that it's a single site but there's a stale DNS entry somewhere that hasn't propagated for some bizarre reason.
Reply
#12
I have had a problem for a while where attempting to login to trac would result in a fail and the site popped-up something about cookies not getting set -- this is using firefox. I have a second, portable install of firefox that I use for testing, and trac was letting me login from that profile so I assume something in my normal profile trac doesn't like. I do have cookies in this profile set by trac so it doesn't seem like a permissions problem, but I don't really know that much about browser/cookie behavior so don't really have a clue how to troubleshoot it.

scott s.
.
Reply
#13
Thanks for that - I saw another issue someone was having with cookies, so I cleared all kodi cookies from my default browser but still it failed. So I tried a different browser, and that failed. So I tried a different system with a different browser - and that failed as well Smile

Basically, any system that I have that uses the 205.a.b.c address will fail, and anything using the 46.a.b.c address will work.

What is possible is that I have a stale DNS record in my server cache, I suppose... I noticed this laptop I'm using here is resolving via resolver1.opendns.com, and that gets the 46.a.b.c address back, so it works; compare that with the example above, which is resolving via localhost. I'll dig further... it may well be that 205.a.b.c is an old address and there simply isn't a site on the end of it any more, which would explain this as well:

http://www.downforeveryoneorjustme.com/205.251.128.242
Reply
#14
Well, that's weird. Seems that dnairb was right...

I normally use Google DNS on my main system - and that resolves trac.kodi.tv to 205.251.128.242.

However, I obviously switched my laptop to OpenDNS at some point (when I was having problems with AmiDuOS, IIRC) - and that was working. So, I've switched my router (and thus all systems) to OpenDNS and they now all resolve trac.kodi.tv to 46.43.42.37. End result: use Google, get the wrong address, use OpenDNS, get one that works.

What's really odd is that "nslookup trac.kodi.tv 8.8.8.8" returns the 46.a.b.c address anyway. Damned if I understand... but I suspect that there simply isn't a Kodi trac system on the end of 205.a.b.c, and wherever that address is coming from needs to be ignored with extreme prejudice.

What's also interesting is that I've been getting a certificate error on kodi.tv for some time - but that's magically disappeared with the switch of DNS servers as well - almost as if the cert was invalid for an old IP address that's still working, and it's that IP that I was hitting...

Anyway, "problem no longer apparent" rather than "problem resolved". Case closed either way.

Thanks for the thoughts, guys - they sent me in the right direction, and maybe this will help someone else.
Reply
#15
I'm currently using my ISP's DNS and get 46.43.42.37. As suggested on the Trac home page, I opened a firefox private window and could login with that.

scott s.
.
Reply
 
Thread Rating:
  • 0 Vote(s) - 0 Average



Logout Mark Read Team Forum Stats Members Help
Can't log in to bug reporting system (Trac)00