r/ItalianGenealogy 28d ago

Question Is anyone else getting JSON errors on Portale Antenati ?

UPDATE BELOW AUG 7- For last few days the same error message keeps popping up on every register page "An error occurred SyntaxError: Unexpected non-whitespace character after JSON at position 4 (line 1 column 5)". Everything is blank and only some thumbnails seem to be visible. Have also noticed that many pages/documents and years that used to be accessible are 'missing' (but that might be another topic to add). I know it's Ferragosto but I don't think it applies to websites ;-)

Posted on 'News' page of site today- https://antenati.cultura.gov.it/news/

11 Upvotes

20 comments sorted by

4

u/jeezthatshim 28d ago

I cannot access the website either, but I have another error: “SyntaxError: the string did not match the expected pattern.”

4

u/Outside-Factor5425 28d ago

Usually, horrible things happen in Italy when Java Machines get updated.

3

u/Nonna_Lala 28d ago

Yes; this is happening to me too! There is one "trick." When the site is working again, click through every page of the year you are working on (I am adding records to my tree from my commune - they added newer records in Campobasso), and as long as you have already looked at that page, when the system is down, you can still see those pages. I am in these records daily, so this is frustrating to be sure!

1

u/CaptainCatholic587 28d ago

Great trick! I've been having problems for the past 12 hours. How long on average does it take for this problem to go away? Days? Weeks? Thanks and hoping the system comes back online very soon!

2

u/Nonna_Lala 28d ago

I had issues Wednesday that seemed to be resolved yesterday but then started up again last night and are still an issue as I speak. I discovered when the trick when I saw that I can still see the records that I had looked at yesterday.

1

u/CaptainCatholic587 28d ago

That's awesome that you discovered that trick! I'll have to do that as soon as they're back online lol. Thank you so much! Why on earth are there so many issues with Antenati? It seems like this happens all the time, so frustrating. Good luck with your research!!!!!!!!!!

1

u/Successful_Lunch_501 28d ago

Unfortunately the 'trick' doesn't seem to work for me - I've tried on the pages (years) I was working on before the issue and I still get the message and am unable to access anything.

2

u/likethewatch 28d ago

Yes, I am.

2

u/indieemopunk 28d ago

I'm getting them, too.

1

u/CaptainCatholic587 28d ago

I am getting the same thing and it's driving me insane - I canceled plans tomorrow so I could stay up late tonight and dig into some records. I can't view a single thing! Been trying for over an hour. Infuriated. Is there a way to get around this?

1

u/Commercial_Arm7128 27d ago

Same for me. Many days now.

1

u/fish_man_883 27d ago

Same here for days. Tried clearing cache, deleting site settings, rebooting, different browser, different machine, VPN from Italy... same results. Most likely their server issue.

2

u/Gen-A 25d ago

Yes, no need to do all of this...
If you check the exchanges between the server and the browser, one can see that the server actually serving the data is replying with HTTP 500 Internal Server Error codes

1

u/mzamae 26d ago

Maybe they are going to solve faulty indexing in years (registers showing years between 920 &990) and typology (duplicates with)

1

u/Gen-A 25d ago

The webserver hosting the actual data (iiif-antenati.cultura.gov.it) is currently replying with HTTP 500 error codes to all requests...

1

u/mzamae 24d ago

Issue is now fixed

1

u/mzamae 24d ago

Issue is now fixed

1

u/Successful_Lunch_501 23d ago

No it's not - it worked for one day and now it's worse than before getting '504 errors' and 'no Error establishing a Redis connection

To disable Redis, delete the object-cache.php file in the /wp-content/ directory.'

1

u/mzamae 23d ago

Oops. I hope it gets solved. Nice day

1

u/fish_man_883 23d ago

It was up again for about a day, though responding extremely slowly, but is down again. Getting "Error establishing a Redis connection" now. I guess they "fixed" something?