I seem to be having a problem running AMFPHP under SSL in our development environment.
I created a self-signed cert under CentOS and got everything working, but whenever I go to the page in Firefox I get warned that the certificate is self-certified and therefore cannot be accepted.
This then seems to affect the AMFPHP calls from flash saying that the certificate was not accepted on the call... Does anyone know a way round this? Is it a setting we can edit locally? Is there something in the AMFPHP config that will ignore this? Or is this happening at a lower level?
Many thanks for any help :)
You can add the certificate as a trusted source but that will only help you on your browser and won't improve the overal experience. Unless it will be fine your you to inform your users to do this (as it is a one off action).
You should also make sure you are using the SecureAMFEndPoint in stead of the regular AMFEndPoint on the ActionScript side.
Related
I have installed the SSL certificate via Cpanel to my WP website. But right after installing it the UI of the website got disturbed.
Without SSL
With SSL
Update 1
I have looked into it and found out that CSS/JS is not properly loaded. So I changed HTTP to HTTPS in my files where I was using it. But still, the issue is the same. Moreover, I am getting the below errors in my console.
Any help would be highly appreciated
Its due to references of css/images/javascript etc that are not using the SSL (https) but use HTTP instead. I recommend to install Really Simple SSL plugin for the quickest solution. Another solution is to go and fix every incorrect reference but this can be a lot of work and may in some cases need advanced knowledge (editing database entries etc.)
Check with your hosting company to properly configure HTTPS Redirects. The hosting company may ask you to install an HTTPS redirect plugin on your website. If that's work out then good if not, then go to PHPmyAdmin of your cPanel and Export your database. Open the database in Notepad++ and replace all http with https . Save the file. Delete old database tables. Import the file you saved with changes. Be aware, it might break your site, so be sure to take a backup of your database before attempting it. If things don't work out, revert the changes and take the help of a developer to fix it for you.
I am trying to obtain some education on websockets but I can't really find a decent tutorial. All tutorials out there instruct you to download a server and teach you how to use it. I'm more interested in how the server actually works and how I can control it on a remote host, like a hosting provider.
Anyway if I wanna learn there really aren't many options other than to download a built server and start inspecting. So I downloaded the server given in this tutorial http://dev.tutsplus.com/tutorials/start-using-html5-websockets-today--net-13270
The problem for now is that I can't even seem to connect to it. I'm running XAMPP on Win7, so it's completely relevant to the tutorial and appears quite easy, however I fail. I've managed to start the server, but when I open client.php I get
Firefox can't establish a connection to the server at
ws://localhost:8000/pol/newWS/server/startDaemon.php. var socket =
new WebSocket(host);
Fortunately chrome appears to provide a more detailed error message
WebSocket connection to 'ws://localhost:8000/pol/newWS/server/startDaemon.php' failed: Error during WebSocket handshake: 'Sec-WebSocket-Accept' header is missing
Javascript's host variable is set to 'ws://localhost:8000/pol/newWS/server/startDaemon.php', that's where the server is located on my localhost. I haven't made any changes to the server. Can anyone help me get this thing going? Thanks in advance!
Websockets in PHP are generally a pain in the ass. Even if you use a library like rachet you need to start it separately, not through a webserver.
As brad said, consider using node.js or the excellent autobahn.ws for python.
I just found some WS server I have downloaded in the past which works pretty well. I can't confirm for any security issues but if anyone knows or finds anything please don't spare us the sharing. I searched for some info in the comments but I couldn't find anything about the creator so I can't really give any credits.
files here
I had FB connect working perfectly fine on my site. Then one day, we noticed it was no longer working. It is not giving any errors, but when I try to do the getUser() function from my facebook class, the response to the send of my signed request is coming back empty, no user data. That is the basic problem, but let me detail what I have nailed down.
I believe there is a problem with the server somehow, either something inside httpd.conf or perhaps php.ini and here is why.
I took all my PHP pages that are required for the FB integration over to another server and another domain. They worked fine. That, to me, ruled out a problem with the code itself, or the Facebook App settings I am using.
I then went back to the problem server, and setup a 3rd domain and tried the same thing again. It would not work. So that, to me, ruled out a problem with the specific domain I am ultimately trying to get working again.
I will admit, I dont know what changes may have been made between the time it was working and when it suddenly was not. If I did, I had a solid idea, I would just roll it back. I did have someone, "recompile apache with mod_deflate and mod_cache." I tried to search for those causing a problem with FB but didnt find anything.
PHP Version 5.3.10
Server version: Apache/2.2.22 (Unix)
Server built: Feb 10 2012 20:31:21
Cpanel::Easy::Apache v3.9.1 rev9999
Thank you for reading my question.
I have resolved my situation. The key to my solution was going to line 633 of base_facebook.php and going an echo $e; to determine why the token response was failing. I then managed to identify the root of the problem:
CurlException: 1: Protocol https not supported or disabled in libcurlCurl
So I contacted my server support people who informed me, "The curl php module has been built without ssl support." which was after they had said
"I am almost positive that when I rebuild apache I made sure curlssl was checked. This is a typical option that people request to have enabled, so I always make sure it is enabled."
So the end solution was that they had to recompile apache and php with the curlssl module.
I'm working on my first web site that requires SSL, it's hosted on a PCI Compliant server, SSL is setup correctly (or so I've been told).
I was hoping that I could just change a particular link in my code to go to a page, such as https://mydomain.com/login.php, but alas, it doesn't work. It doesn't even say that a SSL cert is present.
After some reading I'm thinking I must use curl to correctly work with HTTPS correct? If this is the case, are there any good 'still valid' tutorials on this topic?
Also, my hosting company said I was using php modules(I'm assuming he's referring to functions) that aren't compatible with their systems, they must work with 5.3.x...well I went through an entire page of code they claimed wasn't compatible, and every single function was in the php 5.3.x supported functions list (http://php.net/quickref.php).
Any insight into what they mean here? This stuff shouldn't seem like rocket science, but I'm coming up short on figuring it out correctly, and implementing http with SSL.
Thanks!
I've never heard of this. If mydomain.com/login.php is working but https://mydomain.com/login.php is not then it is not setup. Also you might want to see if https://www.mydomain.com/login.php works. It depends on what was setup as the fully qualified domain name in the certificate and key.
Usually servers have a default self signed certificate and it will give you a warning in browsers when trying to go to https. Is that what you are getting?? Or a different error?
Hope this gives you some direction...If it isn't setup you can go to the CA for directions on install directions.
I know this kind of thing cannot be adequately answered without a link to the live example. Unfortunately, I can't set one up right now as it's a back-end login and creating a safe public login would be too much to do at this point. Sorry. I'm hoping for ideas and input from people who may have experienced something similar in the past.
I am setting up a CMS for a client with a DSL connection in Spain.
The CMS is hosted on a straightforward standard, LAMP based, shared hosting package in a network center in Germany.
It comes with a .com domain.
When my client tries to log in to the CMS using Internet Explorer 7, everything works fine.
When she tries to log in using Firefox, she gets to the login form, submits it - and then the connection times out.
When she logs in using Firefox but using "domain.com" instead of "www.domain.com", everything works fine.
This happens on all computers that are hooked up to that line. One Windows XP, one Windows Vista.
The front-end part of the site, as well as a second, older CMS, work fine in all browsers.
I do not have access to the raw access logs.
I have not been able to reproduce this behaviour on any other connection.
Debugging ideas are welcome. Remote diagnosis is extremely difficult as the line is too slow to set up a proper remote connection.
If you are limited by how you can troubleshoot this, have the client install Fiddler - Web debugging proxy and then run the trace, and send you the logs, Fiddler will analyze the traffic (be it proxy or DNS timeout, etc)
Take a look if you have not used it before:
http://www.fiddler2.com/Fiddler2/version.asp
Check that Firefox and IE are using the same proxy settings.
DNS issues? can you put here your A records to check is everything is ok?