Bitcurator Access: 502 Bad Gateway nginx/1.12.1 (Ubuntu)

24 views
Skip to first unread message

mmwi...@g.harvard.edu

unread,
Aug 20, 2018, 12:10:19 PM8/20/18
to BitCurator Users
All goes well with our install of BC Access (on intel i5, 64-bit Dell) up until we try to open an individual full-text file view. At this point we get the "502 Bad Gateway / hginx/1.12.1 (Ubuntu)" message. This was labeled a bug on 20 December 2017; has there been any progress or workaround found?

Thanks--

Melanie Wisner
Accessioning Archivist
Houghton Library, Harvard University

Kam Woods

unread,
Aug 20, 2018, 12:23:55 PM8/20/18
to bitcurat...@googlegroups.com
It was fixed, but a recent commit broke it in a different way. Working on an update.

Kam

--
You received this message because you are subscribed to the Google Groups "BitCurator Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bitcurator-use...@googlegroups.com.
To post to this group, send email to bitcurat...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/bitcurator-users/97332aab-5163-4b46-8280-a96c11069865%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

mmwi...@g.harvard.edu

unread,
Aug 20, 2018, 1:02:18 PM8/20/18
to BitCurator Users
Thank you! Is this error happening to everyone or is there something about our configuration, OS or hardware or software, that contributes to it?  In other words, is there anything we can do to get started? very eager! 

Melanie

Kam Woods

unread,
Aug 22, 2018, 2:55:43 AM8/22/18
to bitcurat...@googlegroups.com
Should be fixed now in release v0.9.2 and the master on GitHub. Please let me know or open an issue there if you run into additional problems. This software remains in development; further improvements and functionality will be coming soon.

Kam

Kam Woods

unread,
Aug 22, 2018, 3:51:16 PM8/22/18
to bitcurat...@googlegroups.com
Apologies, after looking again it appears there was a bug in the Bootstrap search form as well. Fixed now. The latest tagged release (0.9.6) and master on GitHub should build and run appropriately.

Kam
Reply all
Reply to author
Forward
0 new messages