Just missed 2 for GA for Philly 2. Hope someone here got.
Post edited by Mac57 on
2008 MSG I & II 2010 Newark, MSG I 2013 Wrigley Field, Brooklyn I & II, Hartford, LA I & II, San Diego 2014 Detroit, Moline, St. Paul & Milwaukee 2015 Ed Sullivan Theater/ Central Park 2016 FTL, Miami, Philly 1&2, MSG 1&2, Fenway 1 2017 RRHOF 2018 Seattle I & II, Missoula, Boston I & II 2022 Apollo, MSG, Camden, Nashville & St. Louis 2023 St.P. 1 & 2, Austin 1 & 2
Got the Philly 2 sect 108 row 24 that was just up, happy to be in the building and lower bowl. So 1 for 12 in the check-out.
2008 MSG I & II 2010 Newark, MSG I 2013 Wrigley Field, Brooklyn I & II, Hartford, LA I & II, San Diego 2014 Detroit, Moline, St. Paul & Milwaukee 2015 Ed Sullivan Theater/ Central Park 2016 FTL, Miami, Philly 1&2, MSG 1&2, Fenway 1 2017 RRHOF 2018 Seattle I & II, Missoula, Boston I & II 2022 Apollo, MSG, Camden, Nashville & St. Louis 2023 St.P. 1 & 2, Austin 1 & 2
Thanks, would have rather had the GA that we missed. Keep trying and good luck!
2008 MSG I & II 2010 Newark, MSG I 2013 Wrigley Field, Brooklyn I & II, Hartford, LA I & II, San Diego 2014 Detroit, Moline, St. Paul & Milwaukee 2015 Ed Sullivan Theater/ Central Park 2016 FTL, Miami, Philly 1&2, MSG 1&2, Fenway 1 2017 RRHOF 2018 Seattle I & II, Missoula, Boston I & II 2022 Apollo, MSG, Camden, Nashville & St. Louis 2023 St.P. 1 & 2, Austin 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...
It happens without fail when using my computer at work, and blocks me from using the app. I'm in PHX, but my employer is based in CHI (where I think the ip ultimately routes through).
I can turn off my work Wi-Fi and the app goes back to working again.
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...
It happens without fail when using my computer at work, and blocks me from using the app. I'm in PHX, but my employer is based in CHI (where I think the ip ultimately routes through).
I can turn off my work Wi-Fi and the app goes back to working again.
Yah the only time I've been blocked so far was at work. I have to assume other people that work for the megacorp I work for also use TM, so the traffic must result in blocks from time to time.
I just picked up those F2F Sec. 216 tix for Baltimore! Very happy!
FYI, I switched to use a CC that didn't require extra security/code to be sent, so that helped. Also, when searching I filtered out "Standard" (Balt. added back a bunch of PJ Premium yesterday), so only F2F would show, and then just toggled between asking for 1 and 2 tickets, as there is no F5 (LOL) on the App.
"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
I just picked up those F2F Sec. 216 tix for Baltimore! Very happy!
FYI, I switched to use a CC that didn't require extra security/code to be sent, so that helped. Also, when searching I filtered out "Standard" (Balt. added back a bunch of PJ Premium yesterday), so only F2F would show, and then just toggled between asking for 1 and 2 tickets, as there is no F5 (LOL) on the App.
Congrats
PJ: 2013: London (ON); Buffalo; 2014: Cincinnati; 2016: Sunrise, Miami, Toronto 1-2, Wrigley 2; 2018: London (UK) 1, Milan, Padova, Sea 2, Wrigley 1-2, Fenway 1-2; 2021: SHN, Ohana, Ohana Encore 1-2; 2022: LA 1-2, Phx, Oak 1-2, Fresno, Copenhagen, Hyde Park 1-2; Quebec, Ottawa, Hamilton, Toronto; MSG, Camden, Nashville, Louisville, St. Louis, OKC; 2023: St. Paul 1-2, Chicago 1-2; Fort Worth 2; Austin 1-2
EV Solo: 2017 Louisville and Franklin, 2018 Ohana, 2019 Innings Fest, Berlin, Düsseldorf, Dublin and Ohana; 2021 Ohana Friday (from beach) and Saturday; 2022 Earthlings Newark; 2023 Innings Fest and Benoraya 1-2.
Gutted: London 2 2018, Sacramento 2022, Noblesville 2023
I just picked up those F2F Sec. 216 tix for Baltimore! Very happy!
FYI, I switched to use a CC that didn't require extra security/code to be sent, so that helped. Also, when searching I filtered out "Standard" (Balt. added back a bunch of PJ Premium yesterday), so only F2F would show, and then just toggled between asking for 1 and 2 tickets, as there is no F5 (LOL) on the App.
To quote the 10C from Newsletter #8: "Please understand we have a lot of members and it is very hard to please everybody. If you are one of those unhappy people...please call 1-900-IDN-TCAR."
"Me knowing the truth, I can not concur."
1996: Toronto - 1998: Chicago, Montreal, Barrie - 2000: Montreal, Toronto - 2002: Seattle X2 (Key Arena) - 2003: Cleveland, Buffalo, Toronto, Montreal, Seattle (Benaroya Hall) - 2004: Reading, Toledo, Grand Rapids - 2005: Kitchener, London, Hamilton, Montreal, Ottawa, Toronto, Quebec City - 2006: Toronto X2, Albany, Hartford, Grand Rapids, Cleveland - 2007: Chicago (Vic Theatre) - 2008: NYC X2, Hartford, Mansfield X2 - 2009: Toronto, Chicago X2, Seattle X2, Philadelphia X4 - 2010: Columbus, Noblesville, Cleveland, Buffalo, Hartford - 2011: Montreal, Toronto X2, Ottawa, Hamilton - 2012: Missoula - 2013: London, Chicago, Buffalo, Hartford - 2014: Detroit, Moline - 2015: NYC (Global Citizen Festival) - 2016: Greenville, Toronto X2, Chicago 1 - 2017: Brooklyn (RRHOF Induction) - 2018: Chicago 1, Boston 1 - 2022: Fresno, Ottawa, Hamilton, Toronto, NYC, Camden - 2023: St. Paul X2, Austin X2 - 2024: Vancouver X2, Portland, Sacramento, Noblesville, Philadelphia X2, Baltimore
Is anyone else finding that Ticketmaster is loading/processing super slow when you're trying to get tickets into your cart? If I go to any show and try to add any tickets to my cart, it just chugs and chugs for almost 10 seconds. That can't be helping my cause.
09.24.96 - Columbia, MD / 09.18.98 - Columbia, MD / 09.04.00 - Columbia, MD / 07.01.03 - Bristow, VA / 05.30.06 - Washington, DC / 06.15.09 - Baltimore, MD (Ed solo) / 10.27.09 - Philadelphia, PA / 10.28.09 - Philadelphia, PA / 10.09.10 - Baltimore, MD (Brad) / 10.27.13 - Baltimore, MD / 04.29.16 - Philadelphia, PA / 08.07.16 - Boston, MA / 11.04.16 - Upper Darby, PA (Temple of the Dog) / 04.07.17 - Brooklyn, NY (Hall of Fame) / 09.04.18 - Boston, MA / 03.28.20 - Baltimore, MD / 09.18.21 - Asbury Park, NJ / 05.09.22 - Glendale, AZ / 09.14.22 - Camden, NJ / 09.04.24 - New York, NY / 09.07.24 - Philadelphia, PA / 09.09.24 - Philadelphia, PA / 09.12.24 - Baltimore, MD / Next tour in Seattle??
Is anyone else finding that Ticketmaster is loading/processing super slow when you're trying to get tickets into your cart? If I go to any show and try to add any tickets to my cart, it just chugs and chugs for almost 10 seconds. That can't be helping my cause.
phone or app? might be your internet connection, yeah on laptop, I can hit submit in about 8 seconds, on app/cell its about 15...Which show ?
Is anyone else finding that Ticketmaster is loading/processing super slow when you're trying to get tickets into your cart? If I go to any show and try to add any tickets to my cart, it just chugs and chugs for almost 10 seconds. That can't be helping my cause.
phone or app? might be your internet connection, yeah on laptop, I can hit submit in about 8 seconds, on app/cell its about 15...Which show ?
I've been experimenting... it seems to hold true on my phone (App OR browser) and on my computer (Chrome, Firefox, and Safari). It's just SLOOOW loading all around. I'm trying for Philly 1, but it seems to be the case across the board that it's very slow loading the cart.
EDIT: I guess the real issue is that the slowdown seems to have popped up in the last couple of days. Not like I was successfully getting F2F tickets before then, but the process was quicker.
Post edited by rberko1 on
09.24.96 - Columbia, MD / 09.18.98 - Columbia, MD / 09.04.00 - Columbia, MD / 07.01.03 - Bristow, VA / 05.30.06 - Washington, DC / 06.15.09 - Baltimore, MD (Ed solo) / 10.27.09 - Philadelphia, PA / 10.28.09 - Philadelphia, PA / 10.09.10 - Baltimore, MD (Brad) / 10.27.13 - Baltimore, MD / 04.29.16 - Philadelphia, PA / 08.07.16 - Boston, MA / 11.04.16 - Upper Darby, PA (Temple of the Dog) / 04.07.17 - Brooklyn, NY (Hall of Fame) / 09.04.18 - Boston, MA / 03.28.20 - Baltimore, MD / 09.18.21 - Asbury Park, NJ / 05.09.22 - Glendale, AZ / 09.14.22 - Camden, NJ / 09.04.24 - New York, NY / 09.07.24 - Philadelphia, PA / 09.09.24 - Philadelphia, PA / 09.12.24 - Baltimore, MD / Next tour in Seattle??
Yes, it's been super slow and glitchy the last few days. I've also noticed that if I search while logged in on my computer, I get logged out on my phone. And if I search while logged in on my phone, I get logged out on my computer. Prior to recently, I could just stay logged in on both constantly.
just tossed my 10c's for Van N1 on f2f, section 112 row 6(back of arena straight on view of stage) if anyone looking. Upgraded to my prefered spot, 119 side stage.
Comments
2010 Newark, MSG I
2013 Wrigley Field, Brooklyn I & II, Hartford, LA I & II, San Diego
2014 Detroit, Moline, St. Paul & Milwaukee
2015 Ed Sullivan Theater/ Central Park
2016 FTL, Miami, Philly 1&2, MSG 1&2, Fenway 1
2017 RRHOF
2018 Seattle I & II, Missoula, Boston I & II
2022 Apollo, MSG, Camden, Nashville & St. Louis
2023 St.P. 1 & 2, Austin 1 & 2
2010 Newark, MSG I
2013 Wrigley Field, Brooklyn I & II, Hartford, LA I & II, San Diego
2014 Detroit, Moline, St. Paul & Milwaukee
2015 Ed Sullivan Theater/ Central Park
2016 FTL, Miami, Philly 1&2, MSG 1&2, Fenway 1
2017 RRHOF
2018 Seattle I & II, Missoula, Boston I & II
2022 Apollo, MSG, Camden, Nashville & St. Louis
2023 St.P. 1 & 2, Austin 1 & 2
Gutted: London 2 2018, Sacramento 2022, Noblesville 2023
2010 Newark, MSG I
2013 Wrigley Field, Brooklyn I & II, Hartford, LA I & II, San Diego
2014 Detroit, Moline, St. Paul & Milwaukee
2015 Ed Sullivan Theater/ Central Park
2016 FTL, Miami, Philly 1&2, MSG 1&2, Fenway 1
2017 RRHOF
2018 Seattle I & II, Missoula, Boston I & II
2022 Apollo, MSG, Camden, Nashville & St. Louis
2023 St.P. 1 & 2, Austin 1 & 2
Gone
I can turn off my work Wi-Fi and the app goes back to working again.
Yah the only time I've been blocked so far was at work. I have to assume other people that work for the megacorp I work for also use TM, so the traffic must result in blocks from time to time.
FYI, I switched to use a CC that didn't require extra security/code to be sent, so that helped. Also, when searching I filtered out "Standard" (Balt. added back a bunch of PJ Premium yesterday), so only F2F would show, and then just toggled between asking for 1 and 2 tickets, as there is no F5 (LOL) on the App.
Gutted: London 2 2018, Sacramento 2022, Noblesville 2023
"Me knowing the truth, I can not concur."
1996: Toronto - 1998: Chicago, Montreal, Barrie - 2000: Montreal, Toronto - 2002: Seattle X2 (Key Arena) - 2003: Cleveland, Buffalo, Toronto, Montreal, Seattle (Benaroya Hall) - 2004: Reading, Toledo, Grand Rapids - 2005: Kitchener, London, Hamilton, Montreal, Ottawa, Toronto, Quebec City - 2006: Toronto X2, Albany, Hartford, Grand Rapids, Cleveland - 2007: Chicago (Vic Theatre) - 2008: NYC X2, Hartford, Mansfield X2 - 2009: Toronto, Chicago X2, Seattle X2, Philadelphia X4 - 2010: Columbus, Noblesville, Cleveland, Buffalo, Hartford - 2011: Montreal, Toronto X2, Ottawa, Hamilton - 2012: Missoula - 2013: London, Chicago, Buffalo, Hartford - 2014: Detroit, Moline - 2015: NYC (Global Citizen Festival) - 2016: Greenville, Toronto X2, Chicago 1 - 2017: Brooklyn (RRHOF Induction) - 2018: Chicago 1, Boston 1 - 2022: Fresno, Ottawa, Hamilton, Toronto, NYC, Camden - 2023: St. Paul X2, Austin X2 - 2024: Vancouver X2, Portland, Sacramento, Noblesville, Philadelphia X2, Baltimore
EDIT: I guess the real issue is that the slowdown seems to have popped up in the last couple of days. Not like I was successfully getting F2F tickets before then, but the process was quicker.
2006: Washington, D.C.
2008: Washington, D.C.
2010: Bristow, VA
2013: Baltimore, MD
2016: Hampton, VA
2020: Baltimore, MD
2023: Noblesville, IN TBD