Indy is finally popping a bit. I've picked up 2 reserved singles in the last 15 minutes. Strangely, I was logged out of my account both times, and the payment methods failed to load both times. I thought for sure I'd get u504'd on both. But somehow both sales went thru.
Indy is finally popping a bit. I've picked up 2 reserved singles in the last 15 minutes. Strangely, I was logged out of my account both times, and the payment methods failed to load both times. I thought for sure I'd get u504'd on both. But somehow both sales went thru.
Omg I finally got into the lowers for vegas n2. I just grabbed the laptop and seats popped up immediately..finally. now I can try to move closer but I'm thrilled to actually have a success.
I will be selling my row a sec 210 for vegas
Congrats! Persistence paid off. I’m still hunting for both nights
2005 - London
2009 - Toronto
2010 - Buffalo
2011 - Toronto 1&2
2013 - London, Pittsburgh, Buffalo
2014 - Cincinnati, St. Louis, Detroit
2016 - Ft. Lauderdale, Miami, Ottawa, Toronto 1 2018 - Fenway 1&2 2022 - Hamilton, Toronto 2023 - Chicago 1&2
Well there is a pr in lower bowl for V1. Has them in my cart 3 times this morning and h kept getting the U533 code. What does this mean? finally getting something in cart and not working…ugh
2005 - London
2009 - Toronto
2010 - Buffalo
2011 - Toronto 1&2
2013 - London, Pittsburgh, Buffalo
2014 - Cincinnati, St. Louis, Detroit
2016 - Ft. Lauderdale, Miami, Ottawa, Toronto 1 2018 - Fenway 1&2 2022 - Hamilton, Toronto 2023 - Chicago 1&2
Well there is a pr in lower bowl for V1. Has them in my cart 3 times this morning and h kept getting the U533 code. What does this mean? finally getting something in cart and not working…ugh
Had this happen last year on a timed drop. Seller had to call TM to get account cleared and then relist.
Well there is a pr in lower bowl for V1. Has them in my cart 3 times this morning and h kept getting the U533 code. What does this mean? finally getting something in cart and not working…ugh
Had this happen last year on a timed drop. Seller had to call TM to get account cleared and then relist.
Thanks for reply. I wonder if that’s he issue then, cause they are still up and that will be over an hr now and that shocks me
2005 - London
2009 - Toronto
2010 - Buffalo
2011 - Toronto 1&2
2013 - London, Pittsburgh, Buffalo
2014 - Cincinnati, St. Louis, Detroit
2016 - Ft. Lauderdale, Miami, Ottawa, Toronto 1 2018 - Fenway 1&2 2022 - Hamilton, Toronto 2023 - Chicago 1&2
"McCready played on, lending credence to the theory that he was actually built in Stone’s basement from spare truck parts and vinyl records." - Glide Mag. review of MSG 7/8/03
Those Philly 2’s from last night are on TickPick. I checked as I got the error and the row of that section wasn’t posted. This morning they’re on there for $299. So after fee they will barely make $100 for the pair.
2003: Uniondale, MSG x2 | 2004: Reading | 2005: Gorge, Vancouver, Philly | 2006: East Rutherford x2, Gorge x2, Camden 1, Hartford | 2008: MSG x2, VA Beach | 2009: Philly x3 | 2010: MSG x2, Bristow | 2011: Alpine Valley x2 | 2012: MIA Philly | 2013: Wrigley, Charlottesville, Brooklyn 2 | 2014: Milan, Amsterdam 1 | 2016: MSG x2, Fenway x2, Wrigley 2 | 2018: Rome, Krakow, Berlin | 2021: Sea Hear Now | 2022: San Diego, LA x2, MSG, Camden, Nashville, St. Louis, Denver | 2023: St. Paul 1, Chicago x2, Fort Worth x2, Austin 2
I still don't understand how tickets are sold on sites like TickPick (that aren't MSG or Chi). I know on the other sites people can make burner ticketmaster accounts and just give you the login info. But how does a legit site allow reselling of f2f tickets?
I still don't understand how tickets are sold on sites like TickPick (that aren't MSG or Chi). I know on the other sites people can make burner ticketmaster accounts and just give you the login info. But how does a legit site allow reselling of f2f tickets?
its all just tickets to them. they wouldn't know (or care) it was f2f, right?
Noblesville 5.7.2010. Lexington 4.26.2016. Nashville 9.16.2022. St Louis 9.18.2022. Chicago 1 9.5.2023. Chicago 2 9.7.2023. *Noblesville 9.10.2023* (Gutted)
possibly, but before when I was, it just popped up and said that it thought i was a bot, and couldn't see tickets, but if i refreshed a few times, it let me right back in. This is different. Also, it was doing it like this over the weekend, but only for a little while, then went back to normal. This time it has lasted a lot longer. All that means is that I have to work while im at work now. sucks.
2006: Gorge 1
2009: Seattle 1
2013: Seattle
2016: Wrigley 1 & 2
2018: Seattle 1&2, Montana
2020: San Diego, LA 1&2, Oakland 1&2
2022: San Diego, LA 1&2, Fresno, Sacramento, Las Vegas, Denver
2024: Vancouver 1, Portland, Las Vegas 1&2, Seattle 1&2
I've been dealing with the bot block on my TM account for nearly 2 years, ever since I needed to refresh like mad to buy tickets on the day-of drop for Elton's Farewell tour (ironically because actual bots were buying them all). Through multiple e-mail threads and escalations with TM, they're adamant that there's no type of block on my account. But I hit the dreaded "Your session has been suspended" screen multiple times a day. Though TM was completely unhelpful, I found a workaround.
If you see this message on your desktop, here's what you want to do...
Open your browser's dev tools (I'm using Chrome)... go to wherever you can browse individual session cookies, and find a cookie called 'id-token'.
Delete it.
Refresh and you should be good to go. It appears this doesn't work for everybody, but at least for the type of block associated with my account, this cookie gets created any time I sign in, and clearing it allows me to behave like a regular user again. It does get automatically recreated eventually, even if I haven't signed out, but I can just delete it again and I'm good to go. Unfortunately I haven't found any similar workaround for the mobile app, but this is better than nothing.
Well the tickets that were in Sec 18 for Vegas1 are finally gone. Curious if anyone here got them? They were up for like 5 hrs
2005 - London
2009 - Toronto
2010 - Buffalo
2011 - Toronto 1&2
2013 - London, Pittsburgh, Buffalo
2014 - Cincinnati, St. Louis, Detroit
2016 - Ft. Lauderdale, Miami, Ottawa, Toronto 1 2018 - Fenway 1&2 2022 - Hamilton, Toronto 2023 - Chicago 1&2
I've been dealing with the bot block on my TM account for nearly 2 years, ever since I needed to refresh like mad to buy tickets on the day-of drop for Elton's Farewell tour (ironically because actual bots were buying them all). Through multiple e-mail threads and escalations with TM, they're adamant that there's no type of block on my account. But I hit the dreaded "Your session has been suspended" screen multiple times a day. Though TM was completely unhelpful, I found a workaround.
If you see this message on your desktop, here's what you want to do...
Open your browser's dev tools (I'm using Chrome)... go to wherever you can browse individual session cookies, and find a cookie called 'id-token'.
Delete it.
Refresh and you should be good to go. It appears this doesn't work for everybody, but at least for the type of block associated with my account, this cookie gets created any time I sign in, and clearing it allows me to behave like a regular user again. It does get automatically recreated eventually, even if I haven't signed out, but I can just delete it again and I'm good to go. Unfortunately I haven't found any similar workaround for the mobile app, but this is better than nothing.
the Block is not on your account ... its on your IP address, Wifi or home internet... your IP connection session gets blocked. TMs firewall has a block list, the more you get BOT blocked, TM security will block you quicker... You can try to reset your router and see of a new IP address is assigned, you can also use public wifi like Starbucks... etc...
I've been dealing with the bot block on my TM account for nearly 2 years, ever since I needed to refresh like mad to buy tickets on the day-of drop for Elton's Farewell tour (ironically because actual bots were buying them all). Through multiple e-mail threads and escalations with TM, they're adamant that there's no type of block on my account. But I hit the dreaded "Your session has been suspended" screen multiple times a day. Though TM was completely unhelpful, I found a workaround.
If you see this message on your desktop, here's what you want to do...
Open your browser's dev tools (I'm using Chrome)... go to wherever you can browse individual session cookies, and find a cookie called 'id-token'.
Delete it.
Refresh and you should be good to go. It appears this doesn't work for everybody, but at least for the type of block associated with my account, this cookie gets created any time I sign in, and clearing it allows me to behave like a regular user again. It does get automatically recreated eventually, even if I haven't signed out, but I can just delete it again and I'm good to go. Unfortunately I haven't found any similar workaround for the mobile app, but this is better than nothing.
the Block is not on your account ... its on your IP address, Wifi or home internet... your IP connection session gets blocked. TMs firewall has a block list, the more you get BOT blocked, TM security will block you quicker... You can try to reset your router and see of a new IP address is assigned, you can also use public wifi like Starbucks... etc...
I have disproven that repeatedly. There are multiple types of blocks. The one I've run into is 100% at the account level.
If I change networks (new IP), I still can't buy with my account. And other TM accounts signed into my devices on my home network (same IP that I can't buy with) are able to buy just fine.
There is a TM IP-based block. There is also an account-based block. I've provided a potential workaround for people who run into the latter.
Comments
2009 - Toronto
2010 - Buffalo
2011 - Toronto 1&2
2013 - London, Pittsburgh, Buffalo
2014 - Cincinnati, St. Louis, Detroit
2016 - Ft. Lauderdale, Miami, Ottawa, Toronto 1
2018 - Fenway 1&2
2022 - Hamilton, Toronto
2023 - Chicago 1&2
finally getting something in cart and not working…ugh
2009 - Toronto
2010 - Buffalo
2011 - Toronto 1&2
2013 - London, Pittsburgh, Buffalo
2014 - Cincinnati, St. Louis, Detroit
2016 - Ft. Lauderdale, Miami, Ottawa, Toronto 1
2018 - Fenway 1&2
2022 - Hamilton, Toronto
2023 - Chicago 1&2
https://www.reddit.com/r/Ticketmaster/s/yPRMNWunBX
ISO 2016 Greenville shirt. Size medium. PM me if you have one for sale/trade.
2009 - Toronto
2010 - Buffalo
2011 - Toronto 1&2
2013 - London, Pittsburgh, Buffalo
2014 - Cincinnati, St. Louis, Detroit
2016 - Ft. Lauderdale, Miami, Ottawa, Toronto 1
2018 - Fenway 1&2
2022 - Hamilton, Toronto
2023 - Chicago 1&2
Chicago 1 9.5.2023. Chicago 2 9.7.2023.
*Noblesville 9.10.2023* (Gutted)
2006: Washington, D.C.
2008: Washington, D.C.
2010: Bristow, VA
2013: Baltimore, MD
2016: Hampton, VA
2020: Baltimore, MD
2023: Noblesville, IN TBD
Happened to me most of the day and night yesterday, and so far all day today. it will post tickets for 1 or 2 clicks, then back to that.
2006: Washington, D.C.
2008: Washington, D.C.
2010: Bristow, VA
2013: Baltimore, MD
2016: Hampton, VA
2020: Baltimore, MD
2023: Noblesville, IN TBD
SHOW COUNT: (152) 1990's=3, 2000's=53, 2010/20's=92, US=112, CAN=15, Europe=19 ,New Zealand=2, Australia=2
Mexico=1, Colombia=1
Upcoming: Manchester, London, Chicago x2, NYC x2, Fenway x2, Ohana x2 Aucklandx2, Gold Coast, Melbournex2
I've been dealing with the bot block on my TM account for nearly 2 years, ever since I needed to refresh like mad to buy tickets on the day-of drop for Elton's Farewell tour (ironically because actual bots were buying them all). Through multiple e-mail threads and escalations with TM, they're adamant that there's no type of block on my account. But I hit the dreaded "Your session has been suspended" screen multiple times a day. Though TM was completely unhelpful, I found a workaround.
If you see this message on your desktop, here's what you want to do...Open your browser's dev tools (I'm using Chrome)... go to wherever you can browse individual session cookies, and find a cookie called 'id-token'.
Delete it.
Refresh and you should be good to go. It appears this doesn't work for everybody, but at least for the type of block associated with my account, this cookie gets created any time I sign in, and clearing it allows me to behave like a regular user again. It does get automatically recreated eventually, even if I haven't signed out, but I can just delete it again and I'm good to go. Unfortunately I haven't found any similar workaround for the mobile app, but this is better than nothing.
10/7/96 (FL), 9/22/98 (FL), 9/23/98 (FL), 8/9/00 (FL), 8/10/00 (FL), 8/12/00 (FL), 4/11/03 (FL), 4/12/03 (FL), 4/13/03 (FL), 7/8/03 (NY), 7/9/03 (NY), 7/12/03 (PA), 7/14/03 (NJ), 10/8/04 (FL), 8/5/07 (IL), 11/27/12 (FL), 12/6/13 (WA), 4/8/16 (FL), 4/9/16 (FL), 4/11/16 (FL), 8/5/16 (MA), 8/22/16 (IL), 8/8/18 (WA), 8/10/18 (WA), 9/25/21 (CA), 9/26/21 (CA), 5/3/22 (CA), 5/12/22 (CA), 5/13/22 (CA), 9/18/23 (TX), 9/19/23 (TX), 10/23/23 (WA), 10/24/23 (WA)
2009 - Toronto
2010 - Buffalo
2011 - Toronto 1&2
2013 - London, Pittsburgh, Buffalo
2014 - Cincinnati, St. Louis, Detroit
2016 - Ft. Lauderdale, Miami, Ottawa, Toronto 1
2018 - Fenway 1&2
2022 - Hamilton, Toronto
2023 - Chicago 1&2
Now if I could get paid for the 1800 premium ones.
If I change networks (new IP), I still can't buy with my account. And other TM accounts signed into my devices on my home network (same IP that I can't buy with) are able to buy just fine.
There is a TM IP-based block. There is also an account-based block. I've provided a potential workaround for people who run into the latter.
10/7/96 (FL), 9/22/98 (FL), 9/23/98 (FL), 8/9/00 (FL), 8/10/00 (FL), 8/12/00 (FL), 4/11/03 (FL), 4/12/03 (FL), 4/13/03 (FL), 7/8/03 (NY), 7/9/03 (NY), 7/12/03 (PA), 7/14/03 (NJ), 10/8/04 (FL), 8/5/07 (IL), 11/27/12 (FL), 12/6/13 (WA), 4/8/16 (FL), 4/9/16 (FL), 4/11/16 (FL), 8/5/16 (MA), 8/22/16 (IL), 8/8/18 (WA), 8/10/18 (WA), 9/25/21 (CA), 9/26/21 (CA), 5/3/22 (CA), 5/12/22 (CA), 5/13/22 (CA), 9/18/23 (TX), 9/19/23 (TX), 10/23/23 (WA), 10/24/23 (WA)