<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>The Perceptus Back Story &#187; user interface</title>
	<atom:link href="http://blog.perceptus.ca/category/user-interface/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.perceptus.ca</link>
	<description>Issues and adventures in the life of a Canadian micro-sized geek company</description>
	<lastBuildDate>Tue, 31 Jan 2012 07:11:49 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Troubleshooting &#8220;server-manager&#8221; in SME Server</title>
		<link>http://blog.perceptus.ca/2010/11/19/troubleshooting-server-manager-in-sme-server/</link>
		<comments>http://blog.perceptus.ca/2010/11/19/troubleshooting-server-manager-in-sme-server/#comments</comments>
		<pubDate>Sat, 20 Nov 2010 00:30:30 +0000</pubDate>
		<dc:creator>leonard</dc:creator>
				<category><![CDATA[annoying]]></category>
		<category><![CDATA[SME Server]]></category>
		<category><![CDATA[user interface]]></category>
		<category><![CDATA[980]]></category>
		<category><![CDATA[apache]]></category>
		<category><![CDATA[gui]]></category>
		<category><![CDATA[httpd-admin]]></category>
		<category><![CDATA[proxy]]></category>
		<category><![CDATA[server-manager]]></category>
		<category><![CDATA[sme7]]></category>
		<category><![CDATA[sme8]]></category>

		<guid isPermaLink="false">http://blog.perceptus.ca/?p=333</guid>
		<description><![CDATA[Originally this post was going to document my troubleshooting of my login problem with the web based administrative interface of SME Server 7 after my bare (virtual) metal restore. In the end, I gave up fixing the problem, and did the upgrade via CD to SME Server 8 beta 6.  This didn&#8217;t turn out to be [...]]]></description>
			<content:encoded><![CDATA[<p>Originally this post was going to document my troubleshooting of my login problem with the web based administrative interface of SME Server 7 after my bare (virtual) metal restore. In the end, I gave up fixing the problem, and did the upgrade via CD to SME Server 8 beta 6.  This didn&#8217;t turn out to be an easy fix, and I also had my eye on some nice benefits to upgrading to SME8, such as PHP5 and MySQL5 (finally!)</p>
<p>The following now serves as a review of how I think the &#8220;server-manager&#8221; interface is delivered in SME&#8217;s architecture.  It&#8217;s elegant, but complex.</p>
<p>The exact error was:</p>
<div id="_mcePaste" style="padding-left: 30px;">Forbidden</div>
<div id="_mcePaste" style="padding-left: 30px;">You don&#8217;t have permission to access /server-manager on this server.</div>
<div id="_mcePaste" style="padding-left: 30px;">Additionally, a 403 Forbidden error was encountered while trying to use an ErrorDocument to handle the request.</div>
<p>Unfortunately, I just didn&#8217;t know how to troubleshoot this error.  A lot of the problem was that SME is more complex than your normal web server do to  security precautions.</p>
<p>This is how <em>I think</em> the &#8220;server-manager&#8221; GUI is hosted:</p>
<ul>
<li>You normally go to https://192.168.81.1/server-manager (or whatever your server&#8217;s local IP is)</li>
<li>The web server, &#8220;httpd&#8221;, which runs as user <em>www </em>and group <em>www</em> (which I assume has minimal permissions) then reverse proxies to a second httpd process, httpd-admin</li>
<li>The second Apache server, httpd-admin, runs on port 980, and runs as user <em>admin </em>and group <em>admin</em>.</li>
<li>The 2nd web server has it&#8217;s own configuration files.</li>
<li>The web scripts are in this folder: /etc/e-smith/web/panels/manager/</li>
<li>On a fresh install, the Linux admin user is group id 101, and the admin group is id 101 (my restored server had a different group id)</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://blog.perceptus.ca/2010/11/19/troubleshooting-server-manager-in-sme-server/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>A Fido Customer Relationship Failure: &#8220;Sorry! Your request cannot be completed at this time. Please try again later.&#8221;</title>
		<link>http://blog.perceptus.ca/2010/01/02/fido-website-request-cannot-be-completed/</link>
		<comments>http://blog.perceptus.ca/2010/01/02/fido-website-request-cannot-be-completed/#comments</comments>
		<pubDate>Sun, 03 Jan 2010 07:39:43 +0000</pubDate>
		<dc:creator>leonard</dc:creator>
				<category><![CDATA[annoying]]></category>
		<category><![CDATA[user interface]]></category>
		<category><![CDATA[cellphone]]></category>
		<category><![CDATA[error]]></category>
		<category><![CDATA[fail]]></category>
		<category><![CDATA[fido]]></category>
		<category><![CDATA[fido.ca]]></category>
		<category><![CDATA[login]]></category>
		<category><![CDATA[maintenance]]></category>
		<category><![CDATA[password]]></category>
		<category><![CDATA[user]]></category>
		<category><![CDATA[wireless]]></category>
		<category><![CDATA[wording]]></category>

		<guid isPermaLink="false">http://blog.perceptus.ca/?p=213</guid>
		<description><![CDATA[An example today about how an error message can make the difference between a happy end user, and an annoyed end user that is willing to blog about it &#8211; that&#8217;s me. If you try to login to your account on the Fido.ca website, at about 11:30PM Pacific Time, you will get this error message: [...]]]></description>
			<content:encoded><![CDATA[<p>An example today about how an error message can make the difference between a happy end user, and an annoyed end user that is willing to blog about it &#8211; that&#8217;s me.</p>
<p>If you try to login to your account on the Fido.ca website, at about 11:30PM Pacific Time, you will get this error message: &#8220;Sorry! Your request cannot be completed at this time. Please try again later.&#8221;</p>
<p>On any other website, I would assume that there is a temporary, generally one-time, issue.  Maybe the site is overloaded, or it might have a technical glitch.  That&#8217;s OK.  In Fido land?  This error means that the website is down for it&#8217;s nightly maintenance and I should give up and try tomorrow, but earlier in the night because Fido doesn&#8217;t like people on the West Coast.</p>
<p>This isn&#8217;t listed anywhere &#8211; it&#8217;s  something that I&#8217;ve deduced over months of using the Fido site to pay my bill by credit card.  I&#8217;m not impressed that  Fido&#8217;s website has a nightly maintenance schedule, especially one that seems to kick in before midnight Vancouver time, but I&#8217;m really not impressed by the wording of the error.  All they need to do is follow the banks and fess up to their maintenance schedule. Something like, &#8220;Hi, the Fido.ca user site is unavailable from 11PM to 6AM PST.  Please try again during our operating hours.&#8221;</p>
<p>As an aside, if you&#8217;re wondering what the error message is if you have entered your phone number or password wrong, it&#8217;s &#8220;No match for that phone number and password was found. Please try again&#8230; Sorry! No match was found for that phone number and password. Please retry.&#8221; in a red box right above the login boxes.  I kept getting the &#8220;Please try again later&#8221; error, so at one time I wondered if I had been using the wrong password.</p>
<p>Is this a big enough annoyance to make me switch my cell plan away from Fido?  No, but this added to various other annoyances and&#8230; well&#8230; I&#8217;ll certainly be evaluating my options when the new wireless providers in Canada start up in 2010.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.perceptus.ca/2010/01/02/fido-website-request-cannot-be-completed/feed/</wfw:commentRss>
		<slash:comments>19</slash:comments>
		</item>
	</channel>
</rss>

