Tag Info

New answers tagged

0

SSLProtocol configures which protocols (SSL or TLS) and which specific versions of those protocols will be allowed. For example this: SSLProtocol all -SSLv2 -SSLv3 means enable all supported protocols except SSLv2 and SSLv3. SSLCipherSuite configures which cipher suites can be used. Each of the protocols support different overlapping sets of ciphers; ...


0

With a little digging I was able to resolve the problem. The domain was running PHP as Apache module. When I switched it back to FastCGI, I was able to restore the user permissions to ~username~:psaserv. After that FTP and web services work fine.


0

The solution was considering IPv6 as KM suggested. I replaced those lines with: SetEnvIf Remote_Addr "::1" loopback SetEnvIf Remote_Addr "127\.0\.0\.1" loopback CustomLog logs/access_log combined env=!loopback


0

I recently setup a centos 7 web-server with virtual hosts and I added a <VirtualHost> directive for a blank webpage or coming soon page. This <VirtualHost> directive needs to be above Include conf/vhosts/*.conf in the httpd.conf file.


0

I had a similar problem where I had the following configuration which used to work with Ubuntu 10, but stopped working with Ubuntu 14 (Apache 2.4): <Directory /var/www/vhosts/example.com/httpdocs> Options +FollowSymLinks </Directory> Switching to this sorted the problem (even though the web server user wasn't able to directly access the ...


0

What are these 2a02:1800:100::44:1 and 2a02:1800:100::44:2 doing? They're IPv6 DNS servers. Are they causing that I'm unable to ping to my webpage hosted on my linux? Maybe. It's possible that your network prefers IPv6 over IPv4. If yes: can I remove or shut down these 2 DNS servers? You can remove them, they're just DNS servers that look weird (IPv6 ...


0

The issue turned out not to be file /folder permissions as such, but the security context of the non-working domain. From my limited understanding, in order for Apache to serve up files, the files / folders need to be configured to run under the httpd_sys_content_d context. My 'mistake' was the non-working domain had been mv'd into the Apache content ...


1

you can add mono-repository and then install that. read mod_mono (Ubuntu 13.10 and later, Debian 8.0 and later) section from. http://www.mono-project.com/docs/getting-started/install/linux/ its here: http://origin-download.mono-project.com/repo/debian/pool/main/m/mod-mono/ you can download it by add mono repository to your debian.


0

Apache 2.2 and PHP 5.3 were the versions available in Debian Squeeze (Debian 6). Your /etc/apt/sources.list points to both Squeeze and Jessie (Debian 8), so when you asked to install phpmyadmin, apt-get automatically picked the latest acceptable version and its dependencies; these were taken from Jessie. To avoid this in future, you need to remove the ...


1

It is a reported bug as you can see here: Ubuntu bug-launchpad As you can see in the Bug-Track-Comment, the Bug has been fixed for apache2, but has not been added to the Ubuntu repo yet: John Pye (jdpipe) wrote on 2014-09-04: #9 This bug is resolved by modifying a new 14.04 server to install the apache2 packages from ...


0

You can use setsebool httpd_can_network_connect=1


0

Another option: Create an .htaccess file in your web server root with the following: AddType application/x-httpd-php .htm .html Now apache will process .htm and .html files as php documents and any <?php ... ?> tags located in that file will be interpreted as php.


0

I gather the best solution is to end the php with: header('Location: index.html'); exit;


1

I suppose you could use readfile to dump the file you've just created towards the browser. Alternatively, you could issue a 302 temporary redirect to index.html.


1

It was a simple syntax issue. vim /etc/php.ini ; Maximum amount of memory a script may consume (128MB) ; http://www.php.net/manual/en/ini.core.php#ini.memory-limit memory_limit = 1536 The problem was with the line I had changed. memory_limit = 1536M If you don't specify the suffix indicating the memory allocation, it does memory ...


0

So I've downloaded it manually, and installed under /usr/local/openssl After you do a make install for a library, you need to run sudo ldconfig; this lets the linker know about it. Stuff in /usr/local should then take precedence unless you've changed the linker configuration. Double check you have a libssl with an appropriate creation time in ...


0

This happens to me when my .bash_profile tries to load. I added [ -z "${PS1}" ] && return; At the top and it fixed it


0

if you have a systemd service on CentOs7 you need to stop the service and enable it again to have it fixed systemctl stop httpd vi /usr/lib/systemd/system/httpd.service # add this [Service] UMask=0002 # safe the file with esc ZZ # enable and start apache again systemctl enable httpd systemctl start httpd Then the funny part is that i have chmod 774 ...


1

Your browser will try and match the Subject field of the cert with the HTTP Host Header. AFAIK, you cannot connect to an IP in this manner and expect the SSL certificate to verify ok. (I could be wrong) Additionally, you are using Self Signed SSL certs. Unless you import the CA cert into your browser as a Trusted CA you are always going to get warnings. ...



Top 50 recent answers are included