sorry took me a while to try this - been busy at websci :-)

> As an aside, check your networking setup by doing a double-lookup on
> hostname:

# dig +short cognac.elec.qmul.ac.uk
138.37.xx.xx
# dig +short -x $(dig +short cognac.elec.qmul.ac.uk)

first command gives the ip address.  second command returns nothing.
is this right? what should be in host.conf?  sorry i'm a server admin
noob :-)

-kurt

On Tue, Mar 17, 2009 at 1:19 PM, Tim Haynes <thay...@openlinksw.co.uk> wrote:
> Hugh Williams wrote:
>>
>> Kurt,
>>
>> On 16 Mar 2009, at 18:27, Kurt J wrote:
>>
>>> hmmm
>>>
>>> when i get to step 4 i get a proxy error.  this seems to goto
>>> http://localhost:8890/wiki/.... which firefox doesn't seem to like
>>> ("Proxy server refused connection").   as i'm proxying thru my
>>> localhost ssh tunnel to access the virtuoso instance which is only
>>> facing inside uni.
>>
>> [Hugh] In your virtuoso.ini configuration file what is the value of  the
>> "DefaultHost" param in the "[URIQA]" section as I do believe the
>>  localhost:8890  is being picked up from this setting and you can  change
>> this to the value of the external host name being used.  Although still that
>> should not account for the error you are  experiencing having made the same
>> setting on my server and still  being able to access the Wiki instance
>>>
>>> maybe somehow  it works at uni - i won't know until next week when  i
>>> return.
>>>
>>> i've tried changing conductor->Sys Admin-> Packages -> Framework ->
>>> configure to use cognac.qmul.ac.uk instead of localhost but the wiki
>>> links still seem to point to localhost
>>
>> [Hugh] So you configured a new HTTP listener endpoint to try and  setup
>> the external hostname on ?
>
> As an aside, check your networking setup by doing a double-lookup on
> hostname:
>
> dig +short `hostname`
> dig +short -x $(dig +short `hostname`)
>
> Or just check /etc/hosts, make sure the machine's hostname has a line to
> itself.
>
> ~Tim
> --
> Tim Haynes
> Product Development Consultant
> OpenLink Software
> <http://www.openlinksw.com/>
>

Reply via email to