We strive to make Furkot as bug-free as possible but sometimes things do break. Whenever something unexpected happens please let us know. Send an e-mail or contact us on Twitter or Facebook. If we know about a problem we will be able to fix it faster.
There are several things to look at when Furkot doesn't behave as expected:
While we test Furkot with a wide rage of browsers we cannot support all possible combinations of devices, operating systems and browsers. Furkot works well in the newest versions of Chrome, Edge, Firefox, and Safari. For the best experience we suggest Chrome and Firefox browsers: they are both excellent, easy to install, offer uniform interface on all devices and operating systems, and they are updated frequently and automatically.
With the introduction of Edge, Microsoft is winding down support for Internet Explorer and we decided to stop actively supporting it. Its latest release, IE11, has been around since 2013. It is the only version of Internet Explorer still supported by Microsoft, has quite a few bugs that require special handling and it lacks many features and technologies that Furkot uses. We have to implement numerous workarounds to ensure it works. That slows down Furkot for everybody. Discontinuing support for Internet Explorer allows us to develop new features faster.
Make sure you are using an up-to-date browser: it's important not just because of Furkot - outdated browsers are slower and they can have bugs that make them unsafe to use. Visit WhatIsMyBrowser.com website to confirm that your browser is current and find a newer version if it's not.
Something is wrong with a trip
If the issue seems to be related to the specific trip check and fix warnings: while some - like the warning about weekends - are merely informational, most are a sign that something is not quite right with your trip. Look for stops displayed in red and check their details for the warning explanations. Unless you fix the issues with your trip, certain features - for instance printing or exporting - may not render the results you expect.
We can have a look at your trip if you invite us to share it. Press the share button at the top of the Trip drawer, enter firstname.lastname@example.org as a friend address and your e-mail as From address; then press the Invite button. If you haven't already done so, please describe your problem with a trip in a separate e-mail.
Stop or route is not where you want it
When you type a name of a place or city or select from the Sleep , Eat , and Find drawers, its location may not be where you expect.
Typing the name, make sure to have your map contains the area where the stop you are planning is to increase the chance that Furkot finds it. A stop, especially when inferred from place name, is not guaranteed to be located close to roads: location of a coastal city may fall on the water or a national park may be placed in middle of wilderness. You can always move the stop closer to roads to help Furkot find a route to it.
Content of the Sleep , Eat , and Find drawers is drawn from a number of sources. If you spot an inaccuracy consider contacting the original data provider to correct their data.
Occasionally Furkot will propose a route that is different from what you expected. If that happens make sure your road preferences and mode of travel reflect your intentions. Try dragging the route towards roads you want to take.
Your preferred road may be seasonally closed thus prompting Furkot to route around it. Make sure your trip dates are set to indicate your travel plans and consider seasonal closures. Try the alternative route: it is calculated differently and may be more to your liking.
Furkot uses third party routing engines based on OpenStreetMap to calculate routes. OpenStreetMap is maintained by the community and its data may not always be complete. You can contribute to OpenStreetMap by improving the map and thus the routing data.
If you want us to look at the problem, invite email@example.com to share your trip.
You don't see the trip that you planned
If a trip that you didn't delete cannot be found, please rest assured it's very unlikely that it is in fact lost. We realize that not finding a trip after putting all the effort to plan it is upsetting and we placed numerous safeguards to prevent data loss.
When you don't see the trip you are looking for on the list of your trips, try to reload Furkot webpage: in most Windows and Linux browsers hold down
Ctrl and press
F5. On Mac hold down
Cmd and press
R (in Chrome) or
F5 (in Firefox). In Apple Safari hold down
Shift and click
Reload toolbar button.
Make sure you are signed in with same account you used when initially planning a trip. If you created the trip as a guest, you'll need to use the same computer (phone, tablet) and the same browser to access it.
If you created a trip as a guest and then signed up creating a Furkot account on a different computer or browser, your trip won't be automatically added to your account. In order to bring your trip into your account use the same browser as you used as a guest and sign out from any specific Furkot accounts - that will automatically display your trip in the guest account. As soon as you see your trip, sign in to the account you want to use in the future to access your trip and Furkot will automatically associate it with that account.
Furkot allows you to have more than one account and the trip you are looking for may be associated with a different account. In such case you can transfer the trip from account one account to the other:
Sign into your Furkot account that has the trip you want to transfer.
Invite yourself to share this trip and sign out of the account.
Check your email and accept the invitation signing into your other Furkot account.
Sign back into the first account and change the ownership of the trip to the other account.
At this point you can delete yourself (in your first account) from the trip - if you do that for all trips in this account, it, having no trips, will be deleted after some period of inactivity.
When you employ privacy-protecting measures you are effectively telling the browser to clean your data and forget your activities after you are done. That doesn't include the planned trips but will erase your means of access if you planned your trip as a guest. In such cases regaining the access to your trip may be hard and will require our assistance. If you think that it may be the case, please email us at firstname.lastname@example.org providing as much information about your trip as you can recall: name, dates, names and addresses of stops. If your trip didn't contain many stops, consider recreating it - and consider creating a Furkot account before you proceed with planning.
Automatically scheduled stops
To learn why Furkot added a particular stop select it and click the Settings button. Furkot will display a window with an explanation and settings used to calculate the location of the stop. You can edit settings right there to reschedule or to remove the stop.
Furkot becoming inactive
When you are working on your trip, Furkot constantly sends updates to our servers to save your progress. It is also watching for changes made by your friends with whom you might be sharing the trip. When Furkot detects that it cannot communicate with the servers it switches into view only mode to preserve integrity of your trip. In such cases Furkot displays notification prompting you to refresh the trip.
Seeing the notification occasionally is expected, especially when your Internet connection is slow or unreliable. In rare cases Furkot is unable to maintain a stable connection to our servers which results in an intermittent inactive state. This may be the result of a poor network connectivity, but more often than not it is caused by a 3rd party antivirus software that tries (and fails) to inspect network communication.
Furkot relies on a standard technology of server-sent events. Some antivirus programs and some company firewalls may mistake Furkot connection for a movie or music streaming or a file download either blocking it entirely or delaying it beyond what Furkot can put up with. In this case adding Furkot domain to the list of exclusions in the antivirus program configuration should remedy the problem.
To verify that the problem is caused by blocking server-sent events, open the diagnostics page and check the line labeled Server-sent Events. Send it to us (using the link at its top) if you need help interpreting the results.
Furkot website cannot be reached or rendered
We do our best to ensure Furkot is ready for you 24/7. We monitor our servers from several places all over the world and we try to warn Furkot users whenever we experience any issues that can affect Furkot availability. That said, if you don't see any announcement in our Twitter feed or on our Facebook wall, and if your browser complains that Furkot cannot be reached, make sure to let us know. As always, it helps if you provide us with information about your configuration: open the diagnostics page and click the link at its top to send it to us. Additionally, email us the operating system, type of device, installed browser plugins.
If your browser cannot reach Furkot, there are couple of things you can verify. First of all it's worth checking if the problem that you are seeing affects other users. Visit isup.me and Furkot status page to check if Furkot is accessible from other corners of the Internet.
For security reasons communication between our servers and your browser is always encrypted. Regardless of your browser or operating system you will always have a secure connection indicated by a variation of the green padlock next to Furkot website address. In order to properly secure the connection Furkot refuses to use obsolete encryption protocols. This may cause some antivirus programs, especially the ones performing so called encrypted connection scanning, to interfere with accessing Furkot servers. If Furkot website appears unreachable check your antivirus program settings and disable this feature or add Furkot to the list of trusted websites.
Some of Furkot data is mediated by content delivery network. The purpose of CDN is to speed up loading of Furkot pages and to protect our servers from malicious bots. Without data served by CDN Furkot pages won't rendered correctly and will only show bare-bone textual content.
To determine that your browser can receive all Furkot content, open the diagnostics page and check the line labeled CDN. Send it to us (using the link at its top) if you need help interpreting the results.
Map is blank
Furkot supports a large majority of modern browser and graphics hardware combinations. Occasionally you may see the blank space where the map should be. In most cases it is a temporary issue caused by some incompatibility between the browser and the underlying graphics system.
While we continue to investigate this, you can try the following remedies:
Try Furkot in a different browser. Please know that you'll need to sign up to access your trips in a different browser.
Restart your computer to reset the graphics hardware.
Check that your browser supports WebGL using this simple WebGL demo.
Route does not follow mapped roads
By default Furkot automatically calculates the routes to follow public roads. In most cases such routes closely adhere to mapped roads at any zoom level.
Furkot uses the same underlying OSM data to display the roads on map and to calculate the routes. However the OSM data is processed differently for mapping and for routing. The update schedule may also be different. This may cause the route to occasionally deviate from the mapped roads.
The more twisty is the route, the more resources it takes to display it accurately. Furkot displays routes quickly with limited number of points and then proceeds to a more detailed rendering. Consequently there may be a period, usually brief, when it looks like the route is taking shortcuts and missing roads. If a trip is opened offline without Internet connection, the route may sometimes remain in a state of coarse rendering, seemingly deviating from roads until Furkot connects to the Internet again.
When exporting tracks for a given trip, Furkot limits the number of points per track. Depending on a target device the resulting track may look like it is not adhering to the mapped roads. The GPS device or the navigation app should be able to fill-in the gaps. If not, Furkot allows for exporting high-resolution tracks which include all available points. This option is an exclusive benefit offered to Furkot Pass holders.
Even high resolution tracks can deviate from the mapped roads when displayed by the GPS device or the navigation app. It may happen when the device or the app is using a different mapping system than Furkot. It is less likely when the GPS device or navigation app is based on the same mapping data (OpenStreetMap) as Furkot, but processes them differently, or at a different update schedule.
Uploading the file exported from Furkot to a GPS device or a navigation app
Furkot offers a number of formats and options to export the trip. Finding the format and the set of options suitable for your particular GPS device or a navigation app may require some experimentation. If you want to know how to upload an exported file or why a file fails to upload to a GPS device or a navigation app consult its manual and contact the manufacturer support department. We are unable to offer assistance in handling the third party products.
Furkot supports exporting Garmin route GPX, which includes Garmin proprietary route extensions. While it makes for a better navigation for selected (newer) Garmin models, it is not supported by every type of Garmin device and unlikely to be handled properly by most navigation apps. Contact Garmin representative to verify whether your device supports it.
Uploaded file may be displayed differently in the GPS unit or the navigation app than it is shown in Furkot. While looking for the explanation see the discussion of differences in mapping roads.
We do our best to adhere to the published standards and even proprietary formats supported by GPS devices and navigation apps. Failing to upload is usually caused by mismatch of the selected export options and the capabilities of a GPS device or a navigation app. In many cases it can be remedied by finding the correct set of parameters through experimentation. On the rare occasion that the exported file is not conforming to its specification, you can send it to us for verification. Take care to let us know the exact set of options selected when exporting it and invite us to share the trip from which it was exported.
Troubleshoot the problem
Depending on the problem you can try one of the following remedies. Do not feel like you have to try any of that before contacting us: we are happy that you are using Furkot to plan your trip and we will try to help you as best as we can.
Make sure you are using the latest version of Furkot. Check the More options menu and select the Update Now option if present.
Reload Furkot webpage: in most Windows and Linux browsers hold down
F5. On Mac hold down
R(in Chrome) or
F5(in Firefox). In Apple Safari hold down
Force Furkot to sign you out by clicking the Sign Out button or, if not available, by following this link: https://trips.furkot.com/logout
Check and fix warnings: while some - like the warning about weekends - are merely informational, most are a sign that something is not quite right with your trip. Look for stops displayed in red and check their details for the warning explanations.
Read the manual: many aspects of Furkot are already described in its growing body of help articles. Your problem may turn out to be just a different take on a particular feature.
Some browser extensions, add-ons and plugins that modify page content may interfere with Furkot. Disable extensions - Firefox, Chrome, Internet Explorer, Safari - and, after restarting your browser, try Furkot again. If you discover which extension, add-on or plugin prevents Furkot from working properly, contact us to report a bug and we'll see if we can make Furkot work with it.
If you have an account with Furkot, clear Furkot data from the browser cache. See the detailed instructions for Chrome, Firefox and Safari on Mac and iOS devices. However if you didn't sign up and are accessing Furkot as a guest don't clear the browser cache as it will remove access to your trips.
Find out if the problem persists when you use private or incognito mode of your browser. It's an easy way to try Furkot in fresh environment - without any stale data that may interfere with it. Please know that if you didn't sign up and are accessing Furkot as a guest you won't have access to your trips when browsing in private mode.
Report a bug
We test Furkot thoroughly. That said, we cannot do that in every possible environment. Factors that may influence Furkot behavior include the type of the device, the operating system, the browser, and plugins or add-ons installed in the browser. We count on Furkot users to help us reproduce and ultimately fix the issues. We appreciate the time you take to report an issue and we welcome every bit of information.
We pride ourselves on fixing bugs quickly. Good bug reports certainly help with that. If you need advice on writing good bug reports we can recommend the essay How to Report Bugs Effectively by Simon Tatham.
When reporting a bug start by describing what you did in detail. Assume we exercised this part of Furkot and it worked for us. Since it doesn't work for you, either yours and our setup is different or you and we are doing things differently. Provide as much information as you can to help us identify that difference and reproduce the problem. Don't worry about writing too much. Consider including the following:
If the problem involves a trip invite us to share it. Press the share button at the top of the Trip drawer, enter email@example.com as a friend address and your e-mail as From address; then press the Invite button. If you haven't already done so, please describe the problem in a separate e-mail.
Take a screen snapshot of the problem: in Windows and Linux it's usually as easy as pressing
Prnt Scrbutton. On Mac press
4combination, then press
Spaceand click Furkot window (see how to take screen snapshot on Mac). Sending us a snapshot will help us resolve your issue quicker.
Provide us with information about your configuration: open the diagnostics page and click the link at its top to send it to us. Additionally, email us the operating system, type of device, installed browser plugins.
If you feel comfortable to do so you can also send us the console output. Most browsers will display their internal consoles when you hold down
Jon MAC). Or try
F12and click on the
Consoletab. The console is either displayed in a new window or in a special panel at the bottom of the current browser tab. Select, copy and paste its content or take a screenshot of that window and send it to us.