Topic: Website access problem

[skm]

I setup a SME 7.0 server for mail & website that I can't access "http" but only "https" for the website.

Where can I change the setting for both (http or https) access?

Thanks.

[bpivk]

You should start by telling us where you put/installed your website.
Did you install a contrib or it doesn't work from an ibay?

[skm]

You should start by telling us where you put/installed your website.
Did you install a contrib or it doesn't work from an ibay?

I put the web site in the default web site folder only.
 (/home/e-smith/files/ibay/Primary/html/ )

And I never install any contrib in the server.

[bpivk]

Then report this to the bugtracker if you didn't install any contribs and it's installed in an ibay.

[william_syd]

I setup a SME 7.0 server for mail & website that I can't access "http" but only "https" for the website.

Where can I change the setting for both (http or https) access?

Thanks.

How are you accessing your website. From the 'net with a domain name or from the lan with a IP address?

If https and http both work with a lan ip and https only works with a 'net domain then port 80 could be blocked by your ISP.

[skm]

I setup a SME 7.0 server for mail & website that I can't access "http" but only "https" for the website.

Where can I change the setting for both (http or https) access?

Thanks.

How are you accessing your website. From the 'net with a domain name or from the lan with a IP address?

If https and http both work with a lan ip and https only works with a 'net domain then port 80 could be blocked by your ISP.

Both internal damain & Lan IP are only access by "https".

[william_syd]

I setup a SME 7.0 server for mail & website that I can't access "http" but only "https" for the website.

Where can I change the setting for both (http or https) access?

Thanks.

How are you accessing your website. From the 'net with a domain name or from the lan with a IP address?

If https and http both work with a lan ip and https only works with a 'net domain then port 80 could be blocked by your ISP.

Both internal damain & Lan IP are only access by "https".

Both /server-manager and /webmail do normally redirect to https.

However, out of the box, any other address should be both https and http. Do you have a .htaccess file in your website? What do you see when you try http ?

Yes, do take it to the bug tracker.

[skm]

I setup a SME 7.0 server for mail & website that I can't access "http" but only "https" for the website.

Where can I change the setting for both (http or https) access?

Thanks.

How are you accessing your website. From the 'net with a domain name or from the lan with a IP address?

If https and http both work with a lan ip and https only works with a 'net domain then port 80 could be blocked by your ISP.

Both internal damain & Lan IP are only access by "https".

Both /server-manager and /webmail do normally redirect to https.

However, out of the box, any other address should be both https and http. Do you have a .htaccess file in your website? What do you see when you try http ?


Yes, do take it to the bug tracker.

I don't have a ".htaccess" file in my website.
I input "https://www.domainname.com " that it's ok,
but when I input "http://www.domainname.com " that it shows :
==========================================
Did you mean: "www.domainname.com"  

No standard web pages containing all your search terms were found.
Your search - "www.domainname.com" - did not match any documents.

Suggestions:
Make sure all words are spelled correctly.
Try different keywords.
Try more general keywords.
===========================================

[CharlieBrady]

I setup a SME 7.0 server for mail & website that I can't access "http" but only "https" for the website.

Where can I change the setting for both (http or https) access?

You might need to change your ISP for that. Many ISPs block port 80 access.

[skm]

I setup a SME 7.0 server for mail & website that I can't access "http" but only "https" for the website.

Where can I change the setting for both (http or https) access?

You might need to change your ISP for that. Many ISPs block port 80 access.

It's not the ISP problem, because I had the other Win2K IIS  Web server on the same network and work fine.

[mmccarn]

No standard web pages containing all your search terms were found.
Your search - "www.domainname.com" - did not match any documents.

This is not a normal return value from Internet Explorer or Firefox if you have indeed entered a complete URL (including the "http://").

When you *don't* enter a complete and valid URL your browser tries to do an auto search for the string you entered - in this case the error message is claiming that you entered "www.domainname.com" and NOT "http://www.domainname.com".   I've seen this sort of behavior in computers infected with some sort of DNS hijacking software ("New dot net" was a great one for doing this).

Alternatively, SME by default is trying to proxy your Internet connections, so that whatever you enter needs to be resolvable by the SME server itself as well as your workstation.  For example, if the http proxy is anabled, and I use a VPN to connect my workstation to a client's network, then try to access a website on the client's internal network, I get an error from Squid saying that the website can't be found.  In your case, this would only apply if the value returned by "nslookup www.domainname.com" on your workstation is different from what is returned by the same command in a command shell on the SME server itself.

Finally, what happens if you browse from a workstation on the LAN to http://192.168.x.y (using the LAN IP of your SME box)?

[skm]

No standard web pages containing all your search terms were found.
Your search - "www.domainname.com" - did not match any documents.

This is not a normal return value from Internet Explorer or Firefox if you have indeed entered a complete URL (including the "http://").

When you *don't* enter a complete and valid URL your browser tries to do an auto search for the string you entered - in this case the error message is claiming that you entered "www.domainname.com" and NOT "http://www.domainname.com".   I've seen this sort of behavior in computers infected with some sort of DNS hijacking software ("New dot net" was a great one for doing this).

Alternatively, SME by default is trying to proxy your Internet connections, so that whatever you enter needs to be resolvable by the SME server itself as well as your workstation.  For example, if the http proxy is anabled, and I use a VPN to connect my workstation to a client's network, then try to access a website on the client's internal network, I get an error from Squid saying that the website can't be found.  In your case, this would only apply if the value returned by "nslookup www.domainname.com" on your workstation is different from what is returned by the same command in a command shell on the SME server itself.

Finally, what happens if you browse from a workstation on the LAN to http://192.168.x.y (using the LAN IP of your SME box)?

The "www.domainname.com" only an example. I sured that I'd input a valid link for it and it returned the similar result.

However, same result was returned when I input the Lan ip such as "http://192.168.0.xxx", but it is ok for "https://192.168.0.xxx".