y.st./source/pages/en/weblog/2015/12-December/07.xhtml

<?php
/**
 * <https://y.st./>
 * Copyright © 2015 Alex Yst <mailto:copyright@y.st>
 * 
 * This program is free software: you can redistribute it and/or modify
 * it under the terms of the GNU General Public License as published by
 * the Free Software Foundation, either version 3 of the License, or
 * (at your option) any later version.
 * 
 * This program is distributed in the hope that it will be useful,
 * but WITHOUT ANY WARRANTY; without even the implied warranty of
 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
 * GNU General Public License for more details.
 * 
 * You should have received a copy of the GNU General Public License
 * along with this program. If not, see <https://www.gnu.org./licenses/>.
**/

$xhtml = array(
	'title' => 'Setting up ownCloud',
	'body' => <<<END
<p>
	I went to install ownCloud today, but it seems to have a dependency on Apache.
	The package information says that ownCloud can use either the <a href="apt:apache2"><code>apache2</code></a> or <a href="apt:httpd"><code>httpd</code></a>.
	<code>httpd</code> is a virtual package provided by the <code>apache2</code> package, but it is also provided the <a href="apt:nginx-full"><code>nginx-full</code></a> package, which I installed yesterday.
	Theoretically, Aptitude should not have tried to install Apache.
	In any case, it seemed that I would need to set up Apache if I was to use ownCloud for the time being.
</p>
<p>
	Yesterday, <a href="https://wowana.me/">wowaname</a> talked about the importance of running every onion website on a different port to prevent spoofing attacks that make use of the host name header.
	As such, I set NGINX up on a nonstandard port and set Tor to direct port 443 connections to this other port.
	Knowing that NGINX was running on a nonstandard port so Apache would not clash with it, I reinstalled Apache.
	Somehow, Apache functioned correctly using the same configuration files that were not working yesterday.
	I have no idea what could have possibly have changed.
	The only issue came when I tried to configure Apache to use the port that Tor is redirecting connections to.
	I had forgotten that NGINX was still bound to this port.
	After shutting NGINX down, Apache bound to the port correctly and everything is running fine.
	Why could it not have been this easy yesterday?
</p>
<p>
	I decided to set up ownCloud&apos;s database the easy way, so I tried to install phpMyAdmin.
	I ran into difficulties when setting it up though.
	The install scripts from the phpMyAdmin package wanted to set up phpMyAdmin&apos;s database, but it kept failing to connect to the local database server.
	Eventually, I located the issue: while phpMyAdmin requires a local instance of MySQL in order to function, it does not depend on the MySQL server package.
</p>
<p>
	I found out that every $a[Tor] relay node can be looked up online.
	My node should be listed, but for whatever reason, <a href="https://atlas.torproject.org/#details/0581BFCBE8DDE10719870F19AB08AA515253F485">it is not</a>.
	I restarted my relay while debugging, so it might mess with the uptime stat, but everything on my end looks fine.
	The error log says <q>Dec 07 19:14:35.000 [notice] Self-testing indicates your ORPort is reachable from the outside.
	Excellent.
	Publishing server descriptor.</q>, so my relay should be reachable from the outside world.
</p>
<p>
	My <a href="/a/canary.txt">canary</a> still sings the tune of freedom and transparency.
</p>
END
);