Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I went through your suggested procedure, and after turning off apache, the
ps -ef|grep httpd|grep -v grep command did not show any instances of httpd running on the system.
so.... you may try to find out who is using/blocking port 443 AFTER you stopped the httpd-server you started by yourself.
STOP httpd: "service httpd stop" (or what else you use)
check port 443: "lsof -i TCP:443"
what you konsole shows now, is the programm, that is blocking the port appache would need so hard.
if lsof shows anything up, than you should kill this process by
"pkill processname"
OR
"kill -9 PID"
(.... ok ... it's not a gentle way, but it should work)
btw: if you have just one set of apache-binaries in /usr/sbin-Directory does NOT mean, that there can just be ONE apache-instance running.
you also have just one /usr/bin/konsole-binary, but you can start this binary as much often as you like.
I solved the problem with the redirect. I had a hunch that the iptables file had a syntax error with port 80. I checked it out, and there was indeed such an error. Once I corrected it and restarted the daemon. The redirect worked.
I'm running Apache 2.0.55 on kubuntu.. and I'm trying to redirect traffic on port 80 to 443... I viewed many suggestions... the problem is I'm not finding the file /etc/httpd/conf/httpd.conf (neither the folders httpd and conf)... what shall I do?
I'm running Apache 2.0.55 on kubuntu.. and I'm trying to redirect traffic on port 80 to 443... I viewed many suggestions... the problem is I'm not finding the file /etc/httpd/conf/httpd.conf (neither the folders httpd and conf)... what shall I do?
Thanks in advance...
Hi,
Your configuration files for apache are somewhere else. If Apache is running try...
$ ps -ef | grep httpd
This will show you any httpd processing running. The command line will most likely give you an indication of where you should be looking for the configuration. Check to see if there is an /etc/apache2 directory, the name may be slightly different to the one you expect.
Your configuration files for apache are somewhere else. If Apache is running
try...
$ ps -ef | grep httpd
This will show you any httpd processing running. The command line will most
likely give you an indication of where you should be looking for the
configuration. Check to see if there is an /etc/apache2 directory, the name may
be slightly different to the one you expect.
Regards,
Jim
~~~~~~~~~~
Hey,
Thank you Jim.. I found it in /etc/apache2...
and i succeeded in redirecting my http traffic to https!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.