Fix local trip routing error response

[rachelekm]

As part of the latest release deploy, https://github.com/azavea/cac-tripplanner/releases/tag/3.1.61, local testing of the trip routing appeared broken (see screenshot below). On entering start and end points for directions, trip routing response would immediately error and display broad error message to users. However, app is still able to generate a travelshed and the local OTP site was able to open in browser and successfully route the same start and end points. Trip routing also is working as expected in a deployed environment. This error is likely due to an ongoing issue with latest MacOS version / vagrant + vbox compatibility causing issues connecting multiple VMs on a host-only network.

This issue is to investigate cause of trip routing error from app and fix.