My company is using cfwebsocket on our ColdFusion 11 server. In the past it has worked fine, but recently we started getting this message every time we try to access the page that calls cfwebsocket:
Attribute validation error for the CFWEBSOCKET tag The channel entry specified for subscribeTo is not valid.
"testing123" is not a valid channel registered for this application.
However in our Application.cfc I have setup the channel:
<cfset this.wschannels = [{name="testing123"}] />
Another weird problem is that when I go to the WebSocket section of the ColdFusion Administrator. I get an error as well:
It's really weird because we had this working before. We haven't changed our firewall at all. Can anyone point me in the right direction?
If you have updated to Update 3 then the reason for the problems is due to Adobe breaking websockets in that update.
I submitted a bug just after it was released - http://bugbase.adobe.com/index.cfm?event=bug&id=3865461
Its been fixed and you can request a hotfix from them which does resolve the issue, otherwise you will have to wait until Update 4!
Related
How do I get a registration code or otherwise solve this problem?
While writing this question, I realized the crux of this problem is the bottom-most part of this question: I'm not getting the popup I'm supposed to get and when I enter the URL in a browser it says invalid registration code.
I'm attempting to develop an Alexa Voice Service application. Website/companion service only. I have gone through the Reference Implementation Guide twice and have double checked that all of the setup has been done correctly.
This is the server error I get: invalid registration code. I never did anything with a registration code and can't seem to find anything about a registration code (relevant to Alexa) anywhere after googling quite a bit.
Listening on port 3000
error: { [InvalidRegistrationCode: The provided registration code was invalid.]
name: 'InvalidRegistrationCode',
message: 'The provided registration code was invalid.',
status: 401 }
Error: Can't set headers after they are sent.
Here's the client output:
vlcj: (DefaultMediaPlayer.java:183)
addMediaPlayerEventListener(listener=com.amazon.alexa.avs.AVSAudioPlayer$1#4b3a4950)
There was a problem connecting to the Companion Service. Trying again in 2 seconds. Please make sure it is up and running.
[DEBUG] joining on thread Thread[Timer-0,5,com.amazon.alexa.avs.AVSApp]
There was a problem connecting to the Companion Service.
Trying again in 2 seconds. Please make sure it is up and running.
The AVS launcher opens too, and when I record something and send it I get:
com.amazon.alexa.avs.AVSException: 403 Invalid Access Token
The instructions mention (at the very bottom of the reference guide) that I need to:
Please register your device by visiting the following website on any system and following the instructions: https://localhost:3000/provision/************** That URL is supposed to pop something up once the companion service but that hasn't happened.
Any thoughts on how can I fix this?
I was following a good document Project: Raspberry Pi + Alexa Voice Service at https://github.com/amzn/alexa-avs-raspberry-pi . It describes all steps very well.
Please take a look at the following steps:
3 - Getting started with Alexa Voice Service
3.1 Register for a free Amazon Developer Account
3.4 Register your product and create a security profile.
6 - Enable Security Profile
This thread on the Amazon developer forums seems related: http://forums.developer.amazon.com/forums/thread.jspa?threadID=11327&tstart=0
Quoted response:
There are a number of potential issues causing that error.
You might be sending an invalid scope. Are you sending "alexa:all" as
the scope? Or, your security profile might not be correctly linked. Is
it selected in the dropdown on the developer portal?
Are you getting an access token from the companion service, or is the
text box blank? If you're not getting an access token, check that your
device serial number matches between the companion service and the
java client. If you're getting an access token, the problem is more
likely with your security profile.
You should also look at these threads to see if they're helpful...
(links removed due to reputation requirement)
If that doesn't help, you'll probably have more luck asking the AVS team directly on their forum site.
I've been using Sitecore version 7.1 for a few months now and have noticed that the Sitecore client logs me out after being idle for around 20 mins. Also other users have reported these issues whilst content editing.
I'm using Windows 7, IIS 7, .NET framework 4.5.
I've checked the error log for anything and can see no obvious errors and the keepalive service is running - I get this information in the logs:
ManagedPoolThread #14 12:47:24 INFO Scheduling.UrlAgent started. Url:http://testsite/sitecore/service/keepalive.aspx
I get some of these in the log, but could this be related?
WARN Memory usage exceeded the MemoryMonitor threshold
When I go back to the site after leaving it for say 20 minutes.
I get these entries in the log.
952 15:08:28 INFO AUDIT (sitecore\grahams): Logout
952 15:08:28 WARN Protected page accessed with no current user
6440 15:08:28 INFO AUDIT (sitecore\grahams): Logout
6440 15:08:28 WARN Protected page accessed with no current user
Any body seen this happening before or have any suggests of how I could get to the bottom of this?
Thanks in advance
Ian
We are also experiencing the same or similar problems since upgrading several of our web sites to Sitecore 7.1. We have continued to investigate all of the settings mentioned above but have as yet to find an explanation.
This may help, depending on your situation...Sitecore has confirmed a new issue was introduced: when multiple users login with the same credentials, and one of them logs out, all the others are also logged out automatically.
They have released a temporary hotfix package designed specifically for 7.1 rev. 140130. You should ensure your solution is updated to this version before installing:
https://dl.sitecore.net/hotfix/Sitecore%20CMS%207.1%20rev.%20140130%20Hotfix%20405020-2.zip
Use the Install Package Wizard to apply the hotfix. Hopefully this will be included in the next 7.1 Update package.
UPDATE
I continue to have discussions with sitecore support on this issue and although they have not given me a definite fix or patch, there does seem to be a way to increase the timeout.
This is not without it's side effects but it is at least an option at this point. I am in the process of testing this out myself but I will share for now and update everyone on my progress.
Change or add the following three settings in your web.config (in the example below the timeout is 2 hours):
Client Timeout
<setting name="Authentication.ClientSessionTimeout" value="120" />
Forms Timeout
<authentication mode="None">
<forms name=".ASPXAUTH" cookieless="UseCookies" timeout="120" />
</authentication>
Session Timeout
<sessionState mode="InProc" ... timeout="120" />
There are a couple of configurations you need to checkout.
There is a client timeout setting in Sitecore:
<setting name="Authentication.ClientSessionTimeout" value="60"/>
Check that this is not set to 20 minutes.
Further you should check your session timeout here:
<sessionState mode="InProc" stateConnectionString="tcpip=127.0.0.1:42424" sqlConnectionString="data source=127.0.0.1;user id=sa;password=" cookieless="false" timeout="20"/>
I've experienced this is issue with Sitecore 8.2 rev 170728 (Update 5). In my case, the cause of the issue was that I was accessing the site through HTTP while the following setting in the web.config file was not allowing it:
<httpCookies httpOnlyCookies="true" requireSSL="true" />
The issue can be fixed by either making sure you access the site through HTTPS or by setting the attribute "requireSSL" to "false" in the above setting.
I am currently running Coldfusion 8,0,1,195765 on a Windows 2003 SP 2 server over IIS 6.0.
I needed to change one of the Mail Server Settings in the ColdFusion Administrator, but when I clicked Submit Changes, the page appeared to refresh, and the field was reverted.
I made a change to another page to make sure that changes could be made, and sure enough, the change was applied.
There are no errors shown - everything looks normal, aside from the change.
I was able to make my changes programatically, using mail.cfc, and my change did appear in CF Admin.
My concern is that mail functions have been corrupted or compromised - my primary request for the stackoverflow gurus is how can I restore my Mail Server Settings functionality?
My secondary request is How could this have happened?
Thank you for reading my question.
I am having a similar problem with debugging.
Regarding your first question... You can access the administrator api programatically. Here's how you can verify connection and verify what the current settings are:
<cfscript>
/* you must log in first */
adminObj = createObject("component","cfide.adminapi.administrator"); // this assumes default installation
adminObj.login("password"); // enter your cf admin password
mailServerObj = createObject("component","cfide.adminapi.mail");
value = mailServerObj.getMailServers();
</cfscript>
<cfdump var="#value#">
Value is an array of your current mail server settings.
To make a change change the last part of your script to:
mailServerObj = createObject("component","cfide.adminapi.mail");
mailServerObj.setMailServers(
"yourMailServer",
portNumber,
username="yourUsername",
password="yourPassword",
priority="yourServerPriority");
value = mailServerObj.getMailServers();
The only required value is the entry for yourMailServer. Also, the optional value, portNumber, must be numeric.
Check out http://livedocs.adobe.com/coldfusion/8/htmldocs/help.html?content=basiconfig_37.html for the Adobe documentation for using the Administrator API.
You can also see a complete listing of the Administrator API CFC and their respective functions, check out http://www.cfexecute.com/admin-api-documentation/
I'm using Recaptcha within Django. I was using the following tutorial to integrate it in my web application: http://www.marcofucci.com/tumblelog/26/jul/2009/integrating-recaptcha-with-django/
The captcha doesn't show up on my machine. Instead of the captcha the following error message is displayed:
An internal error occurred: 4A6376441D250.ADE1949.3546A435
(I get a different code each time).
To which domain did you sign the recaptcha? If you entered "127.0.0.1" in the registration make sure you use this one and not "localhost".
Today, I got this error on one of my client's website.
It was working great but suddenly it stop working. Then upon googling I find this link and renewed my API key.
But after I switched to Secure (SSL Enabled) side of my website then It stops working again.
Then, In I got this function there
recaptcha_get_html(PUBLIC_KEY, $error, true);
The third argumentation use the SSL Server, I've to enable it.
This fixed everything for me.
In Coldfusion 8 Enterprise (8,0,1,195765), the following two lines of code causes this error:
Unable to read the source URL. Status Code: 400 Try adding or changing UserAgent attribute in the CFFeed tag
<cffeed source="http://twitter.com/statuses/user_timeline/62944327.rss" query="twitter">
<cfdump var="#twitter#">
Yet, on my development box with Coldfusion 8 Standard (8,0,0,176276), it's working.... Argh. Any ideas why?
Not sure, but possibly it is caused by rate limiting as explained on this page
http://apiwiki.twitter.com/HTTP-Response-Codes-and-Errors
and this page:
http://apiwiki.twitter.com/Rate-limiting
Does the server running Enterprise have to go through a proxy to get out? I've had that happen before with cfhttp, it works on dev but not in production because the production box goes out through a proxy and you have to supply the proxy info to make it work.