Koozali.org: home of the SME Server
Obsolete Releases => SME 8.x Contribs => Topic started by: emshu on January 28, 2015, 10:39:01 AM
-
Hello. I ran into a problem. My created website opens with https. How can I make it to http? Because I want this website reached by other people in the internet and I do not need secure connection. Any ideas?
Thank you, Emshu
-
Nothing to do, just access it over http (do not type https in your browser)
-
emshu
You tell us very little information about your system, ie where you installed the web site etc, so here is a guess.
Perhaps you enabled Force secure connections (ie https) in server manager Information bays setup.
It should typically be Disabled.
-
What information do you need? By the way, i disabled the force secure connection (it was enabled) . Not I cannot access the website. Any way to undo this ,if i can't reach the server manager? But I can log in as root via putty.
-
emshu
Please tell us everything you can about what it is, how & where you set it up, any custom settings that may turn on https etc etc etc.
ie
is it installed in an ibay (what name) or primary or /opt ?
what is the web app ?
how did you install it, ie from a contrib or manually following what instructions etc ?
Have you installed other apps or contribs on the server (if so what are they) ?
are there any other custom configurations that you have made to the server ?
Have you looked in the hhtp & https log files (in /var/log/....... to see what is happeneing when you access the web site ?
Log files can also be accessed from server manager
What is the history of your server, new install or upgrade from version xxx or restore from a backup ???
Did this or other web sites work OK previously on this server ?
Have you done any recent upgrades or changes etc or installed another web app etc?
What is the web site URL so we can check from externally ?
What information do you need? By the way, i disabled the force secure connection (it was enabled) . Not I cannot access the website. Any way to undo this ,if i can't reach the server manager? But I can log in as root via putty.
It sounds to me like there is code or a redirect or maybe unusual permissions in your web app that may be forcing https
Server manager can also be accessed in text mode,
at the root prompt type console (or alternatively login as admin instead of root), then select server manager from the menu
What are the log files saying now you cannot access the web site ?
You need to be much more verbose about your system & what you have done etc, you cannot expect us to be mind readers & keep blindly guessing.
After having made that ibay change, you could try doing
signal-event post-upgrade
signal-event reboot
to see if that improves the situation
-
It's installed in ibay/kompai. Installed following contrib instructions. No other apps were installed. There are no custom configutarions. And I cannot even access server manager now in text mode. It says server manager not available. All websites on server went down when I changed "Force secure connection" to disabled (following tip above). Now I cannot undo that, cannot access server manager from anywhere. Tried configuring configuration.php file and tried changing force_ssl to 0 and to 1 and to 2. Nothing changed in either way. Sorry if I don't give much information, but i'm new at this.
-
What have you installed ? a Joomla instance ? What do you have when you try to reach the server-manager ? an error message ? which one ?
-
Server runs joomla. And the error is "This webpage is not available. Error code: ERR_CONNECTION_REFUSED " (I'm translating this from my own language) . And I get the same error when I try to access any website that is on that server.
-
Ok, this means apache is not running at all. If you have no customization, please open a bug on the bugtracker, explain what yoiu've done to get this error (so a dev can reproduce it) and add the output of:
httpd -t
Thanks
-
emshu
Please re-read my answer, there are many other questions you have not answered & information you have not provided.
Please look at the log files, You can access them via root & cd to /var/log/..... (the appropriate log file (many possibilities so look)).
You say you are a newbie, so it's time to learn.
Number 1 tip is to read the log files & quote error messages fully & accurately as both those they will most likely give good clues.
Also look in the messages log file as well as the various http files
We cannot see or read these, so you are our eyes & you need to do the looking.
-
Syntax error on line 136 of /etc/httpd/conf/httpd.conf:
SSLCertificateFile: file '/home/e-smith/ssl.key/www.kompiuteriai.eu.key' does no t exist or is empty
This is the output of httpd -t . I have no idea how to do the other thing you asked, Damen
-
emshu
Clearly your system has some (multiple ?) problems.
lI have no idea how to do the other thing you asked, Damen
Daniel was asking you to open a bug report at Bugzilla, as he feels your problems could be better resolved via the Bugzilla web pages.
Remember bugzilla is for problems that are potentially bugs, so you do not need to have determined whether a bug exists or not. Experts at Bugzilla will do that.
Click on the Bugs link at top of these Forums, if you have never used Bugzilla before you will need to create a new login which requires a valid email address as your user login name.
Then lodge a new bug report & just select the SME server version & a category (as best you can) & clearly & fully state your problem & provide log file entries, error messages etc.
You will be asked & guided to provide further information so be ready to follow up.
Finally post the bug number URL here for future reference & follow up.
-
Ty everyone for help. I restarted server and databases from backups, everything works now. I haven't found a way to undo the changes but server reinstall :)
-
emshu
Well it was most likely changes you made to the server that caused your problem(s). These could include manual configuration changes, custom template changes & installation of contribs, but you never gave us a chance to find out what was wrong.
When you make future changes, only do one change at a time & then test server is functioning OK, that way you will see immediately if a change causes a problem & you can either revert to the previous state or troubleshoot the one specific issue.