Topic: HELP:Sme Server - Web Server

[bpivk]

443 is HTTPS port.

Well did you mess with iptables? Because it should work stock.

On the port-forwarding panel, forward port 8080 (or whatever) to port 80 and try that port.

[rockyoyster]

I did not mess with anything. I was looking through them. But I dont touch!!

I don't follow the port forwarding. My panel only allows me to forward ports to IP's, but there are no options to forward ports to ports. I'd like to forward port 80 to port 403 or some other open port. But I don't see anything like that.

 I was contemplating looking through the tables of apache or some other server that actually works and see if there are any noticable differences..

[rockyoyster]

Because port 80 is stealth, could it be that SME  is expecting to see it; but it's not. So it is dropping the packet or it just times out? Is that an option with IPTABLES? I don't see anything in the log files to prove this but maybe I'm not seeing the right log files... hmmmm

[bpivk]

I did not mess with anything. I was looking through them. But I dont touch!!

I don't follow the port forwarding. My panel only allows me to forward ports to IP's, but there are no options to forward ports to ports. I'd like to forward port 80 to port 403 or some other open port. But I don't see anything like that.

 I was contemplating looking through the tables of apache or some other server that actually works and see if there are any noticable differences..

My mistake. I was thinking of sme server-manager pannel. I guess that i should point that out.
Use the sme port forwarding function to forward to another port (eg. 8080 localhost 80).

Your server should work if you say that you didn't touch anything. The only other thing could be that your ISP blocks port 80 but if you say that it worked before...

[rockyoyster]

It is running in Server Only Mode and port forwarding is not available. It is only available in Gateway Mode.

[bpivk]

It is running in Server Only Mode and port forwarding is not available. It is only available in Gateway Mode.

Umm. Could be. I never ran my server in server-only mode.

Did you try to run it on a dmz line?

[rockyoyster]

I am going to use port 8080. I will forward the router to port 8080. I am going to change  80 to 8080 in httpd.conf. Do I also need to change this in MASQ and/or IPTABLES? Or is there a command I can issue that will send all 8080 requests to 80 and vice versa?

[bpivk]

How do I allow public access to a service I've added to SME7?
The procedure has changed and is now much simpler in SME7. For this example the service you have installed is called 'manta' and 'nnn' is the TCP port number that needs to be opened. Watch your capitalization with the command below:


config set manta service access public status enabled TCPPort nnn
For UDP services, use UDPPort instead of TCPPort.
Note that you can also set restrictions with AllowHosts and DenyHosts:


config setprop manta ~AllowHosts 1.2.3.4,10.11.12.0/24
config setprop manta ~DenyHosts 16.17.18.18
Then, to activate, do:


signal-event remoteaccess-update

Got this from the old wiki.

[rockyoyster]

I think we are good now. I did the CONFIG command. It did change the ports but there was still no access. I changed the 80 to 8080 on the Listen line in HTTPD.CONF and it works. I also changed the 80 to 8080 in the MASQ file. Everything appears to be working so far.

 It appears that my ISP is stealthing the popular ports;atleast thats all I can come up with right now. However, I would be interested in knowing why I was able to run the XAMPP with the exact same setup no problem. I think I will dig through some config files and see if I can come up with anything.

 Thanks for you help. I would have otherwise abandoned this a few days ago. Can I offer you some coffee?

[bpivk]

Your server should work if you say that you didn't touch anything. The only other thing could be that your ISP blocks port 80 but if you say that it worked before...

I was asking this question myself a few posts earlier.

But you'll have to template your changes if you want to keep them after a reboot.

Code: [Select]


#mkdir -p /etc/e-smith/templates-custom/etc/httpd/conf/httpd.conf
#cp /etc/e-smith/templates/etc/httpd/conf/httpd.conf/35Listen80 /etc/e-smith/templates-custom/etc/httpd/conf/httpd.conf/35Listen80
#mcedit /etc/e-smith/templates-custom/etc/httpd/conf/httpd.conf/35Listen80
#/sbin/e-smith/expand-template /etc/httpd/conf/httpd.conf
#service httpd-e-smith restart

This should do it.

[rockyoyster]

I will have to look into the blocking of the ports. They would have had to of done this quite recently. I had the other server going just a few weeks ago. If the port is Stealth, does that make it completely inaccesible?

Welp, thanks for you help again. For now the 8080 will do just fine.

[bpivk]

If the port is Stealth, does that make it completely inaccesible?

Yes. Closed means that the port is closed and stealth means that the port doesn't even seem to exist.

For now the 8080 will do just fine.

Ok but you really need to template it or you'll lost your changes after the next upgrade.

[rockyoyster]

All Done.. It's a good thing you mentioned the templates. I had no clue! I wold have been in a world of confusion all over again! Thank you!!