Okay, I've fixed and re-enabled HTTPS for apertium.org. For posterity: 1. Run pip --version, discover pip is 18 versions old. Uninstall pip from package manager and install via get-pip.py. 2. Run virtualenv --version, discover virtualenv is N > 10 versions old. Upgrade virtualenv using new pip. 3. Re-run certbot initial setup (works now!). 4. Verify crontab upgrade still works (it does).
Omitting the banging-head-against-wall between steps 1 and 2. I also bumped the site up to v3.2.17 while I was at it, making live the new(ish) Arabic and Galician translations! [image: Sushain Cherivirala] *Sushain K. Cherivirala * Stanford University, M.S. in Computer Science '19 Carnegie Mellon University, B.S. in Computer Science '18 (713) 992-4043 | www.skc.name On Fri, Apr 12, 2019 at 10:20 AM Sushain Cherivirala <sush...@skc.name> wrote: > Okay, took care of that. Things should work on http now until we can get > certs working again. > > > On Fri, Apr 12, 2019 at 10:06 AM Sushain Cherivirala <sush...@skc.name> > wrote: > >> The new issue is simple. In config.conf, APY_URL is currently set to >> https://www.apertium.org/apy. >> Changing it to http://www.apertium.org/apy and running make will fix it. >> >> [image: Sushain Cherivirala] >> *Sushain K. Cherivirala * >> Stanford University, M.S. in Computer Science '19 >> Carnegie Mellon University, B.S. in Computer Science '18 >> (713) 992-4043 | www.skc.name >> >> >> On Fri, Apr 12, 2019 at 7:23 AM Francis Tyers <fty...@prompsit.com> >> wrote: >> >>> El 2019-04-12 08:17, Sushain Cherivirala escribió: >>> > Hi Mikel, >>> > >>> > Unfortunately, the certificate expired a couple weeks ago. I chatted >>> > with Fran a couple >>> > days ago and attempted to fix it. However, the Let's Encrypt client >>> > software doesn't work >>> > well with the old version of Debian installed on xixona and I don't >>> > have access to perform >>> > any detailed debugging or figure out how to install an older version >>> > of the software and >>> > prevent it from self-updating again (there's a cron that renews the >>> > cert but also by default >>> > updates the software). >>> > >>> > My simple suggestion was to remove the line in the Apache config that >>> > redirects http to >>> > https, at least preventing the site from being entirely unusable. IMO, >>> > the preferable option >>> > is just to redirect apertium.org [1]'s DNS entries to Tino's projectjj >>> > server (already used by >>> > beta.apertium.org [2]). Then, Fran, myself and others can make sure we >>> > don't end up here >>> > again since we'll have direct access. >>> > >>> > SUSHAIN K. CHERIVIRALA >>> > >>> > Stanford University, M.S. in Computer Science '19 >>> > Carnegie Mellon University, B.S. in Computer Science '18 >>> > >>> > (713) 992-4043 | www.skc.name [3] >>> > >>> > On Thu, Apr 11, 2019 at 11:56 PM Mikel L. Forcada <m...@dlsi.ua.es> >>> > wrote: >>> > >>> >> Dear all, >>> >> >>> >> When trying to access apertium.org [1] from the Universitat >>> >> d'Alacant, >>> >> browsers suggest that you should not do it because it is not a >>> >> trusted >>> >> site. Also, when using the Apertium web server from inside OmegaT, a >>> >> >>> >> security error pops up. I don't know if I can do anything myself, >>> >> does >>> >> anyone know how to solve this? >>> >> >>> >>> I tried acme.sh but it didn't work (see the IRC logs) >>> >>> I managed to turn off the SSL redirect, but translation is not >>> working via the website. Although at least it now appears. >>> >>> Fran >>> >>
_______________________________________________ Apertium-stuff mailing list Apertium-stuff@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/apertium-stuff
