I'm trying to setup a local red5 streaming server to stream my desktop screen to multiple devices with no luck. the setup will eventually look like this.
mylaptop screen (live stream)=> red5 server <= client devices pulling the live stream
note: red5 server is ubuntu based, client devices will eventually be android tablets but any device will do just fine for now
This is what I have so far:
1) Installed red5-server and all of its dependencies using apt-get install red5-server
2) Downloaded red5-screenshare applet from http://code.google.com/p/red5-screenshare/
and followed all the steps there
3) After I start my screensharing, visiting the client link http://[my_red5_server:5080]/screenshare/screenviewer.html produces error #2032
chrome developer tools says
GET http://my_red5_server:5080/screenshare/textLayout_1.1.0.604.swz 404 Not Found
4) so I downloaded the textLayout file from adobe, placed it into the screenshare folder but I still get the same 404 not found error
Is my setup wrong? I'm not sure how to debug this since there's very few documentation on the matter and I reeeeally dont want to write my own java app and reinvent the wheel
Also if any of you happy hackers have found a different solution to locally screenshare I'm all ears
Thank you for taking the time to help.
The error your getting is because the flex "swz" files cannot be downloaded from Adobe. This was happening to us at work this week and we solved it by finding the offending files via google and placing them on our server. Download the swz files and place them in the same directory as your swf file.
Related
So far I managed to capture the traffic of local Java programs & Android browser successfully. However, I failed to capture traffic of my Android application (using HttpsUrlConnection).
While following the steps in this guide to configure the WiFi network on the device, in the step of downloading the certificate I faced an odd behavior as Chrome raised an error and Firefox installed it without opening the expected dialog:
But when I try to download it again, it says that the certificate is already installed.
Anyway, when running my app (on a real device, Karbonn S203 API 19), there are no requests nor tunnels logged in Fiddler. I tried a lot including inspecting this thread to no avail. In other articles I read about showing tunnels only but I don't have them either. Am I missing anything?
Thanks.
EDIT: I managed to install is "correctly" (with the above screen) from Settings -> Security -> Install Certificate after copying if from PC. Still I cannot see the requests in Fiddler.
Apparently the problem occurred due to using some uncommon devices (well, at least uncommon in Europe/North America). They've probably made some configuration changes in their AOSP version. When working the same way with Nexus 5 I managed to add the ceritifcate under 'WiFi' and then captured requests successfully.
Looks like your app does not use Fiddler as a proxy. When you call openConnection do you pass a Proxy object to it? If so, how do you initialize this proxy object?
You might want to try sending some HTTP traffic through first to make sure you are using the correct proxy settings and then try with HTTPS.
[Update: Problem Solved, Clear solution unable to be achieved. More information in comments]
I am new to azure and I am attempting to create a API Application following the tutorial found here https://azure.microsoft.com/en-us/documentation/articles/app-service-api-java-api-app/
Everything works fine on the local machine but when I attempt to push it to the live site and do a Postman request for http://talkapi.azurewebsites.net/api/contacts/2 I get resource not available.
I don't know what bugging tools I have and where to start. I was wondering if anyone had some advice on where to start debugging or what the problem is.
According to the tuturial and per my experience, it seems that the issue of 404 not found was caused by the incorrect deployment on Azure.
Please access the link https://talkapi.scm.azurewebsites.net/DebugConsole the Kudu tool of your API App and move to the path D:\home\site\wwwroot\webapps, then you will see the fig below.
Try to drag your ROOT.war file and drop here (\webapps), and tomcat will auto-decompress the war file and replace the directory ROOT, then you can try to request the api http://talkapi.azurewebsites.net/api/contacts/2 again.
Kudu is the engine behind git deployments in Azure Web Sites includes Azure API App, you can see more detals at https://github.com/projectkudu/kudu/wiki.
Hope it helps. Any update, please feel free to let me know.
I've been using XAMP and it's features for some php sites and it's working fine. I'm now needing to use it for JSP development for a project we're about to start working on.
So far it's functioning on my local machine in that I downloaded the sample war file from Tomcat and it deploys fine and is visible when using localhost:8080/sample.
The problem is that I can't seem to access it from a browser using the domain name. I tried www.mydomain.com/sample but receive a 404 error.
The same when using my local IP address instead.
I've searched online for a while now and have come across a few sources that hint at integrating apache with tomcat but nothing concrete enough to try and get a working solution.
I've also tried (and miserably failed) to watch the video that is referenced in a few other questions.
Any help is hugely appreciated,
Thanks.
that's because tomcat works on port 8080 unlike apache - when you run php sites they are just behind the apache which is visible on port 80 (which the default one in browsers), you can go through "http://mydomain.com:8080/sample" and it would work the same as through localhost
you can also change tomcat's settings and change it's connector's port from 8080 to 80, and then it would work as you expected
What steps should I take to correctly deploy Playframework 2.1.1 website on production server?
More specific questions:
1) Should I install Play on my production server?
2) Locally it is clear to use play run but in production I need to run it 24/7 and restart it again if server has been restarted. How this works? Some outostart or something?
3) How to deploy it on Ubuntu 12.04(Apache2) server on mydomain.com(port 80)?
4) What configuration settings should I change/add for production to disable debug etc.?
I would really appreciate information about default deployment workflow for Playframework 2.1.1
First create a deployable version of your project using play clean compile dist.
The documentation recommends play clean compile stage but the dist command generates a nice ZIP file and does basically the same things.
You then load that file onto your server and extract it to the desired folder. Now start the Play server with the start file Play created for you.
Play defaults to TCP port 9000 as it does in debug mode but you can change that by using the option -Dhttp.port=80. Listening on a specific IP address can be done via -Dhttp.address=127.0.0.1.
But the thing I do is using an nginx as a reverse proxy to control things link GZIP compression and to listen on a specific hostname. Just search the web for more details about reverse proxies.
You should have an own configuration file for your production use because you need to turn off evolutions, change the database server, and maybe some other stuff you added during development. More about the production configuration can be found in the docs.
I followed the recaptcha instructions and created a simple app that works if I run it in Eclipse using a local Tomcat server but the same files give an error (verify-params-incorrect) when validating the user's response when run in Eclipse using the local Google App Engine SDK.
Are you using the Java code linked to on the reCAPTCHA site? I took a quick look at it, and I suspect that the SimpleHttpLoader class uses some Java classes that are no allowed by Google's AppEngine.
So, here is what I know: Running locally, I get the same error as you.
But, when I deploy it to AppEngine, it works! For the forum posts I've read, I suspect it has to do with the remote IP address (127.0.0.1) when running locally.
This is sort of an impertinent answer, but are you sure you really need to pester your potential users with a captcha at all? There's a great article over on sitepoint entitled "10 Things to Check Before Using a CAPTCHA"
I had no problems at all locally with Google App Engine or deployed with recaptcha4j-0.0.8.jar and Google App Engine SDK 1.6.6. I followed the reCaptcha tutorial for Java at https://developers.google.com/recaptcha/docs/java.
Check here for recaptcha4j lastest version: http://code.google.com/p/recaptcha4j/downloads/list