<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#ffffff">
On 09/14/2010 09:33 AM, Mark Adams wrote:
<blockquote cite="mid:4C8F95D2.1000303@msn.com" type="cite">
<meta http-equiv="content-type"
content="text/html; charset=ISO-8859-1">
Okay, I have mythweb and mythfrontend running on my primary server
which is open to the Internet. I can see that port 6543 is open on my
network and forwarded to the mythbackend running on my htpc (which is
not the primary server facing the Internet).<br>
<br>
Trouble is, when I point my browser to
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://">http://</a><my.domain>/mythweb,
I get:<br>
<br>
<div id="message">
<h2>Error</h2>
<p>
Unable to connect to the master backend at 127.0.0.1:6543 (hostname:
pvr).<br>
Is it running?</p>
</div>
I get this whether I'm forwarding that port on my router or not. I
have configured mythtv-setup's backend settings and mythfrontend's
setup both to point to the backend on my htpc. I've tried it by
hostname and by IP address (I can connect from the server to the htpc
just fine by either hostname or IP).<br>
<br>
Now, unless I'm missing something, the master backend address in the
error above should be showing the ip address of the htpc and not the
loopback address of anything. The master backend on the htpc is
running btw. I can connect to mythweb running on the htpc from within
my lan just fine. I want to be able to connect to mythweb running on
the server from the Internet.<br>
<br>
And here's a funky piece of information that confuses me more. If I
forward port 6543 on my router to my htpc, a port scan on my domain
shows that port open. <br>
<br>
<blockquote type="cite">nmap my.domain<br>
<br>
Starting Nmap 5.00 ( <a moz-do-not-send="true"
class="moz-txt-link-freetext" href="http://nmap.org">http://nmap.org</a>
) at 2010-09-14 09:27 MDT<br>
Interesting ports on xxx-xxx-xxx-xxx.albq.qwest.net (xxx-xxx-xxx-xxx):<br>
Not shown: 995 closed ports<br>
PORT STATE SERVICE<br>
xxx/tcp open xxxxxx<br>
xxx/tcp open xxxxxx<br>
xxx/tcp open xxxxxx<br>
6543/tcp open mythtv<br>
</blockquote>
<br>
If I forward that port to my web server, it does not show up in a basic
port scan:<br>
<br>
<blockquote type="cite"># nmap my.domain<br>
<br>
Starting Nmap 5.00 ( <a moz-do-not-send="true"
class="moz-txt-link-freetext" href="http://nmap.org">http://nmap.org</a>
) at 2010-09-14 09:27 MDT<br>
Interesting ports on xxx-xxx-xxx-xxx.albq.qwest.net (xxx-xxx-xxx-xxx):<br>
Not shown: 996 closed ports<br>
PORT STATE SERVICE<br>
xxx/tcp open xxxxxx<br>
xxx/tcp open xxxxxx<br>
xxx/tcp open xxxxxx<br>
</blockquote>
<br>
Those scan are all taken with firewalls down.<br>
<br>
Does this look familiar to anybody?<br>
<br>
Any ideas?<br>
<br>
Mark<br>
<pre wrap="">
</pre>
</blockquote>
Okay, I just read my own post and it appears that when I forward the
port to my server, it is one of 996 closed ports. I have no idea how to
open that port up. Again, no firewall and iptables on the server is
stopped.<br>
<br>
I still don't know.<br>
<br>
Mark<br>
<br>
</body>
</html>