tedwin
Well-known member
- Joined
- Jun 2, 2008
- Messages
- 70
- Reaction score
- 1
Received this e-mail from Webervations today:
Dear Innkeeper,
We're writing to let you know about an important change to Webervations. As of March 15, 2012, we will no longer accept FTP (file transfer protocol) connections to Webervations. What this means for you is that if your property management software still uses FTP to upload availability to Webervations or download reservations from Webervations, then your software will no longer be able to communicate with Webervations.
Due to the insecure nature of FTP, the FTP communication method has been phased out for many years in favor of the more secure SSL (HTTPS) method. While most property management systems have switched to SSL communication, there are still some systems which only support FTP. This includes the following systems: Guest Tracker 2.x/3.x, Innovation, GuestAll, TCS GuestTracker, Dabble, Innkontrol, InnReserve, and Motelmax.
Securing your data is very important to us, and we are making this change as part of our overall PCI and security compliance efforts, in order to ensure that Webervations is the safest and most secure online booking system available.
Please contact your property management software vendor to see if they have an updated version of your software which supports HTTPS communication. If an updated version is not available (for example, no update is available for Guest Tracker 2.x/3.x), we may be able to migrate your data to the RezOvation property management system, which links to Webervations for uploading availability and downloading reservations.
If you are interested in migrating to RezOvation, please contact the RezOvation team at 877-239-1398 option 1.
Thank you,
Webervations Support
Perhaps I'm the last of dying bred -- the Webervations user. This change will kill our modus operandi and without very much lead time to scramble and find a viable alternative. Their rational for doing it is sound but most Webervations users aren't in the market for a product as pricey as RezOvation. Fortunately, I am already working on the transition to ReservationKey.
Dear Innkeeper,
We're writing to let you know about an important change to Webervations. As of March 15, 2012, we will no longer accept FTP (file transfer protocol) connections to Webervations. What this means for you is that if your property management software still uses FTP to upload availability to Webervations or download reservations from Webervations, then your software will no longer be able to communicate with Webervations.
Due to the insecure nature of FTP, the FTP communication method has been phased out for many years in favor of the more secure SSL (HTTPS) method. While most property management systems have switched to SSL communication, there are still some systems which only support FTP. This includes the following systems: Guest Tracker 2.x/3.x, Innovation, GuestAll, TCS GuestTracker, Dabble, Innkontrol, InnReserve, and Motelmax.
Securing your data is very important to us, and we are making this change as part of our overall PCI and security compliance efforts, in order to ensure that Webervations is the safest and most secure online booking system available.
Please contact your property management software vendor to see if they have an updated version of your software which supports HTTPS communication. If an updated version is not available (for example, no update is available for Guest Tracker 2.x/3.x), we may be able to migrate your data to the RezOvation property management system, which links to Webervations for uploading availability and downloading reservations.
If you are interested in migrating to RezOvation, please contact the RezOvation team at 877-239-1398 option 1.
Thank you,
Webervations Support
Perhaps I'm the last of dying bred -- the Webervations user. This change will kill our modus operandi and without very much lead time to scramble and find a viable alternative. Their rational for doing it is sound but most Webervations users aren't in the market for a product as pricey as RezOvation. Fortunately, I am already working on the transition to ReservationKey.