SOLVED: Amahi not loading after comment port 443 in ssl.conf

[sinexi]

Hi,

I've had to comment out lines with port 443 in the /etc/httpd/conf.d/ssl.conf file. Because httpd (Apache) was listening in on port 443 instead of Mono. My other application works now but the Amahi console now doesn't.

I don't know why because Amahi console just runs on port 80 right?

[bigfoot65]

Details!

What version of Amahi/OS? Did you do any manual configuration changes?

Yes Amahi uses port 80 primarily.

[sinexi]

Sure.

I'm using Fedora 19 with Amahi 7 installed on top.

I've made manual changes to the file /etc/httpd/conf.d/ssl.conf by commenting out 2 lines below.

#
# When we also provide SSL we have to listen to the
# the HTTPS port in addition.
#
#Listen 443 https <- Commented out

##
## SSL Global Context
##
## All SSL configuration in this context applies both to
## the main server and all SSL-enabled virtual hosts.
##

# Pass Phrase Dialog:
# Configure the pass phrase gathering process.
# The filtering dialog program (`builtin' is a internal
# terminal dialog) has to provide the pass phrase on stdout.
SSLPassPhraseDialog exec:/usr/libexec/httpd-ssl-pass-dialog

# Inter-Process Session Cache:
# Configure the SSL Session Cache: First the mechanism
# to use and second the expiring timeout (in seconds).
SSLSessionCache shmcb:/run/httpd/sslcache(512000)
SSLSessionCacheTimeout 300

# Pseudo Random Number Generator (PRNG):
# Configure one or more sources to seed the PRNG of the
# SSL library. The seed data should be of good random quality.
# WARNING! On some platforms /dev/random blocks if not enough entropy
# is available. This means you then cannot use the /dev/random device
# because it would lead to very long connection times (as long as
# it requires to make more entropy available). But usually those
# platforms additionally provide a /dev/urandom device which doesn't
# block. So, if available, use this one instead. Read the mod_ssl User
# Manual for more details.
SSLRandomSeed startup file:/dev/urandom 256
SSLRandomSeed connect builtin
#SSLRandomSeed startup file:/dev/random 512
#SSLRandomSeed connect file:/dev/random 512
#SSLRandomSeed connect file:/dev/urandom 512

#
# Use "SSLCryptoDevice" to enable any supported hardware
# accelerators. Use "openssl engine -v" to list supported
# engine names. NOTE: If you enable an accelerator and the
# server does not start, consult the error logs and ensure
# your accelerator is functioning properly.
#
SSLCryptoDevice builtin
#SSLCryptoDevice ubsec

##
## SSL Virtual Host Context
##

#<VirtualHost _default_:443> <- Commented out

[bigfoot65]

There is something wrong with your HDA or install as those should be fine uncommented. I have checked mine and works fine.

Did you do any other manual configuration or add anything not from the Amahi store?

You mentioned Mono. Is that something you installed?

EDIT: Messing with those files will likely break Amahi. Recommend you put things back the way they were originally.

[sinexi]

That's good to hear.

I did install Mono via RPM manually. I'll try uninstalling Mono and see if that works. If not, I'll back all my files and do a fresh install.

[bigfoot65]

Ok. Uninstalling should be work.

Have to be careful what you manually install as not all packages play nicely with Amahi.

[sinexi]

It did work. Re-installed Fedora 19 from scratch.

Thanks

[bigfoot65]

Good to hear. Lesson learned, careful what you add LOL