I am successfully running an Amazon S3 bucket as media.mydomain.com. The problem is, I'm running an https site and I'm unable to link to files using https//media.mydomain.com. How can I switch to using SSL?
I'm using Laravel Forge + Digital Ocean for hosting and deployment, in case that matters.
I'm getting a 413 error on my laravel forge site using nginx.
I updated php.ini for cli and ftp to 1000m and updated my nginx config for client_max_body_size = 1000m. Still getting that 413. The file I'm trying to upload is 6 megabytes.
Is there a log file that I can peruse that would help me troubleshoot that further? How should I better troubleshoot this error?
I'm currently running 5.3.17 and I'd like to update to the latest stable version. I've looked up a bunch of guides and they all have me doing it manually using wget. I'd like to do it all through zypper so that I can update it using 'zypper update' like I do with most everything else.
How can I update php to the latest stable using zypper?
I've got an Amazon ec2 instance running OpenSuse and I'm getting a white page of death on some of my php scripts but there's no error log in var/log/apache2. To my surprise, there's also no access log.
Is this disabled by default? How do I enable error and access logging?
Edit:
In case this helps, when I set display_errors in php.ini to On, it displays this error:
Parse error: syntax error, unexpected '[' in /srv/www/htdocs/application/controllers/browse.php on line 165
But it doesn't get logged anywhere that I can find.
I'm running OpenSSH 5.3p1-81.el6_3, which according to my server is the latest stable version. My PCI scan is showing CVE-2010-4478 and CVE-2011-0539 exploits as being present due to my OpenSSH version.
Checking "rpm -q --changelog openssh" shows that there have been updates as late as october 2012. Surely these have been resolved? There are newer versions of SSH (6.x I believe) but from what I can tell, rehat/centos backports security fixes to old stable versions like 5.3.
Are these fixed in my version or aren't they? If yes, how can I show this to my PCI scanner to prove a false positive?
Thanks!
And is it necessary? I've read a bunch of pages on it and I can't for the life of me actually figure it out, as opposed to what apache and just plain old php already do.
I'm getting 9 second load times on a very powerful server. Query time is .05 and total php time is 9 seconds. Not good!
I took a look at my list of apache modules and I'm wondering if there's a culprit in the bunch:
Asis
AuthnDefault
Env
Expires
Fileprotect
Frontpage
Headers
Mod SuPhp (especially this one, what does it do? I've never seen this before on our other servers)
Proxy
Version
Bcmath
CHI
Calendar
Curl
CurlSSL
FTP
FileInfo
GD
Iconv
Imap
Magic Quotes
Mbregex
Mysql
Mysql of the system
OpenSSL
POSIX
Path Info Check
Pear
Phar
SQLite3
Sockets
Zip
Zlib
Any ideas?
I was presented with an argument to the tune of "you don't need a strong mysql user password because in order to use it, they'd already have access to your server." We're talking about a 4 digit password that is a standard english dictionary word on a live business website.
Without influencing the answers with my own knowledge and experience, I'd like to show them some responses from a disinterested 3rd party source. Anyone care to chime in on this one? Programming / practical answers would be appreciated.