July 31, 20241 yr Have been using the latest version without any issues since it came out. But now whenever I try to start P2ATC I get this error message: "Internet Access Problem. Unable to initiate session with License Server. Please check your internet connection and security settings to be sure Piot2ATC has access to the web." My internet connection is working fine, and I haven't changed any security settings or made any other changes to my PC. And now I also can't get to the pilot2atc.com site to open. Anyone know what's going on? Gary M. | PPL ASEL | System Specs: W11 Pro, Corsair 4000X Mid Tower, Z790 Aorus Master Motherboard, i9-13900KF, 64 GB DDR5 SRAM, RTX 4090, Dell AW3821DW Monitor, Honeycomb Alpha & Bravo, MFG Crosswind Pedals, TrackIR
July 31, 20241 yr Author It's working now and i can get to pilot2atc.com. Must have been some kind of temp server issue. Gary M. | PPL ASEL | System Specs: W11 Pro, Corsair 4000X Mid Tower, Z790 Aorus Master Motherboard, i9-13900KF, 64 GB DDR5 SRAM, RTX 4090, Dell AW3821DW Monitor, Honeycomb Alpha & Bravo, MFG Crosswind Pedals, TrackIR
August 16, 20241 yr Author OK, this happened again today. Is anyone else having this issue? Just trying to figure out if it's something on my end or something temporarily going on with the program and website that is affecting all users. Gary M. | PPL ASEL | System Specs: W11 Pro, Corsair 4000X Mid Tower, Z790 Aorus Master Motherboard, i9-13900KF, 64 GB DDR5 SRAM, RTX 4090, Dell AW3821DW Monitor, Honeycomb Alpha & Bravo, MFG Crosswind Pedals, TrackIR
August 22, 20241 yr Author Well, I had 318 people view my post. And no one said they have seen this. So I guess it's something on my end. Gary M. | PPL ASEL | System Specs: W11 Pro, Corsair 4000X Mid Tower, Z790 Aorus Master Motherboard, i9-13900KF, 64 GB DDR5 SRAM, RTX 4090, Dell AW3821DW Monitor, Honeycomb Alpha & Bravo, MFG Crosswind Pedals, TrackIR
December 16, 20241 yr On 8/22/2024 at 9:43 AM, TexasGary said: Well, I had 318 people view my post. And no one said they have seen this. So I guess it's something on my end. At the time, probably, it was not you, but the backend, as it has happened again earlier today (see below). Today's issue has since been sorted, I was unable to access P2A only less than an hour. In the thread linked below, Dave acknowledges this is a problem and will look into implementing some improvements (backend with better uptime). Fingers crossed.
Create an account or sign in to comment