|
By powery - Saturday, April 27, 2013
|
Hello,
I have these error mesages in log by generating the report after server upgrade:
HTTP Error 404: file not found
https://familytrees.genopro.com/powery/GenoProCache.xml
HTTP Error 404: file not found
https://familytrees.genopro.com/powery/thumbnails/GenoProCache.xml
HTTP Error 404: file not found
https://familytrees.genopro.com/powery/genomaps/GenoProCache.xml
HTTP Error 404: file not found
https://familytrees.genopro.com/powery/scripts/GenoProCache.xml
|
|
By genome - Friday, May 10, 2013
|
This error has been occurring since GenoPro moved its familytrees site to a new server. I suspect a server side script has been omitted or is not functioning correctly.
The error does not seem to affect the generated report. The checksums in GenoProCache.xml file are used by the Narrative Report to determine whether or not thumbnails have been updated since the report was last generated and by GenoPro to decide whether or not pages and been updated and need to be uploaded. Perhaps Jean-Claude can throw some light on this?
|
|
By powery - Monday, October 5, 2015
|
Hello,
I have the similar issue again.
An error occurred in the secure channel support
https://familytrees.genopro.com/powery/GenoProCache.xml
|
|
By vlepore - Monday, October 5, 2015
|
|
I happen the same problem. You can not perform the update of the site of familytrees.genopro.com when the file GenoProCache.xm is very large: Connecting to server familytrees.genopro.com... The attempt to connect to theserver failed; please verify firewall settings, server name and port number https://familytrees.genopro.com/vlepore/GEMONA/GenoProCache.xml ……. The File GenoproCache.hml is very large (9.66 MB)
(Ibelieve there is this problem with GenoPro2016)
Should always erase everything and start again?
|
|
By GenoProSupport - Tuesday, October 6, 2015
|
|
To my knowledge familytrees.genopro.com does NOT support HTTPS. We are in the process to buy a wildcard certificate to secure *.genopro.com, however we still need to assign an IP addresse for each sub-domain to secure.
|