Hi. I have problem with account verification. What is the cause of this error? "5 : Get request not successful: 302"
Alternate with "TLS waiting for file"
What I did:
1. Twitterdub and roaming folders to av exclusions
2. Python Set Process Identifier
Get request not successful: 302
- martin@rootjazz
- Site Admin
- Posts: 34816
- Joined: Fri Jan 25, 2013 10:06 pm
- Location: The Funk
- Contact:
Re: Get request not successful: 302
https://rootjazz.com/twitterdub/updatetesting.html
should handle the 302 issue
for "waiting for TLS file".
It's either lost connection to the tls browser: if so, try TOOLS > PYTHON ENV > SET PROCESS IDENTIFIER > enter any new ID
should handle the 302 issue
for "waiting for TLS file".
It's either lost connection to the tls browser: if so, try TOOLS > PYTHON ENV > SET PROCESS IDENTIFIER > enter any new ID
Re: Get request not successful: 302
I downloaded update. Still the same problem.
- martin@rootjazz
- Site Admin
- Posts: 34816
- Joined: Fri Jan 25, 2013 10:06 pm
- Location: The Funk
- Contact:
- martin@rootjazz
- Site Admin
- Posts: 34816
- Joined: Fri Jan 25, 2013 10:06 pm
- Location: The Funk
- Contact:
Re: Get request not successful: 302
Update version downloaded. This error still occurs. I have several accounts. which I cannot log in.
- martin@rootjazz
- Site Admin
- Posts: 34816
- Joined: Fri Jan 25, 2013 10:06 pm
- Location: The Funk
- Contact:
Re: Get request not successful: 302
as above, the update gives me more logging to find out what is happening.
you need to send me your logs:
Please perform:
1) Clear logs: HELP > LOGS > DELETE
2) Run the action that you are having an issue with. Login attempt
Goto the ACCOUNTS tab
Check the account
Uncheck option to USE EXISTING COOKIES (if option exists)
Check Force
click the link VERIFY:LOGIN
This will create an action and send it to the PROCESSING TAB
Goto the processing tab and click RUN. The action will run.
You can double click the action to view the logs and submit logs.
***
IDEALLY PLEASE DO NOT RUN ANY OTHER ACTIONS AT THE SAME TIME
***
3) If the issue happens again, submit logs:
HELP > LOGS > SUBMIT
then send your logs ID - the first 4 numbers is sufficient (displayed after successful uploading of logs)
Regards,
Martin