Interactive Family Tree doesn’t work on my Mac, I get “failed to load file” error. This has been the case in 5.1.6 and now in 5.2 On my Linux box it works just fine.
Does any Mac user know how to fix that?
I have never used that before, but when I tried it now, it opens a github link in the browser.
https://pewu.github.io/topola-viewer/#/view?utm_source=gramps&handleCors=false&standalone=false&url=http://127.0.0.1:8156/
Definitely looks like a bug somewhere. I couldn’t find anything like this on bugtracker, so I entered a bug, 0013201
Do you see your tree displayed in that browser window? Or do you get an error message like me? On Linux, that link displays what I consider the best looking, interactive view of your family tree. Clearly there is some issue on the Mac which I would dearly love to find out.
Despite looking like an external link, your data (according to developer) never leaves your computer
It just opens a browser window with an error message “Failed to load file”.
It appears that the viewer can’t access the Gedcom file that Gramps makes. Perhaps the way that Gramps sets up the http server doesn’t work in macOS, or macOS is preventing the browser script from accessing the Gedcom file.
There is an issue on the topola github page that appears to relate to this. It refers to the browser being blocked from accessing localhost.
https://github.com/PeWu/topola-viewer/issues/82
1 Like
Good find, thank you. I changed to Firefox and it works just fine. It also works fine with Chrome. So the issue is with Safari not being able to access localhost. I will post here if I find solution, thanks again.
Is there a way to set the browser for Gramps? Or did you have to change the default browser for everything?
There is a setting in Safari to “disable local file restrictions”, but this didn’t fix it for me.
Perplexity recommendations:
To address the issue of Safari prohibiting access to localhost, you can make changes to allow this access. One common problem is Safari forcing HTTPS on localhost. To resolve this, you can try the following steps:
- Bypassing HTTPS on Localhost: You can bypass HTTPS on localhost by modifying your server configuration or using tools like ngrok to create a secure tunnel without HTTPS.
- Check Security Settings: Ensure that your security settings in Safari are not overly restrictive, as this can sometimes prevent access to localhost.
- Clear Cache and Cookies: Clearing your browser cache and cookies might help resolve any issues related to accessing localhost.
- Update Browser and OS: Keeping your Safari browser and operating system up to date can also help resolve compatibility issues with localhost access.
By following these steps, you should be able to address the problem of Safari blocking access to localhost effectively.
Global change. This is really weird, if you copy just the http://127.0.0.1/8156 part of the address and paste it into a new Safari window, it displays content in a text form. So there must some access there to the localhost. It looks like some security setting. I am not running a server, only standard browser which should be sufficient. Clearing history and cookies made no difference.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.