I'm building a web based client with strophe and jquery and I'm using openfire as server.
Almost everything its working, I can get the roster list, send and receive messages, but when I'm trying to change my presence from avaliable to xa or dnd or any other else the server stops answering and I start to get 404 errors on my POSTs and invalid SID messages like this: "NetworkError: 404 Invalid SID. - http://myurl.com/".
I've been through other topics around and it seems to be a problem with my avaliable credentials, but I don't have any clear evidence of what's wrong.
thanks in advance for any help.
I'm also using Strophe and for me everything works just fine! I don't know what could be you problem, since you didn't share your code with us, so my answer probably won't help you, but here's what I do to update my presence:
connection.send($pres().c('status').t('dnd or any status you want'));
Related
Need Help!
I have been trying to reissue SSL in namecheap.com. I have already created multiple CSR using MacOS Keychain (Both from the Philippines, and from Japan) and through AWS. However, when I get to the Review & Submit part I keep getting an error (screenshot below). Thank you for any assistance with this, as I have tried numerous methods, and I still could not update the SSL.
I have gotten in touch with namecheap.com, and their response is
"... the certificate has this issue due to a bug from our side that is connected to .ink TLD. ..."
It seems that this is a bug in their system.
If anybody gets this error, you might want to connect with namecheap.com, to see if this bug is still not fixed.
Whenever I try to log into github from IntelliJ, I get this error.
Even thought my authentication data is correct, it tells me it's not. And it doesn't matter if I use a token or just use my credentials. I get the same problem. I've tried to delete all tokens and generated a new one, this also didn't change anything. What could be the problem? Thanks.
The issue might be caused by some proxy in the middle. Invalid authentication data is a generic message that appears when call to GitHub API fails without clear reasons. Connection reset seems to be the real message, and could be caused by some proxy or network firewall.
Check the logs for more details on the error. If you think it is some bug in IntelliJ, it is worth reporting the issue to http://youtrack.jetbrains.com/ with logs attached.
I am currently having some issues with heroku. I just installed it and tried to heroku create. It takes my credentials but so far i just get this
! HTTP Error: https://api.heroku.com/login 410 Gone
! Invalid response from API.
! HTTP 410
! {myMail myPw}
!
! Are you behind a proxy?
! https://devcenter.heroku.com/articles/using-the-cli#using-an-http-proxy
I have been looking around for others with that issue but they all were behind a proxy. I am not. I also checked my firewall settings and also tried to run the command line client with admin rights. But nothing has proven to be successful so far. I'll keep trying and post an answer as soon as i figure it out. Maybe someone of you has an idea. Would be appreciated. Thanks in advance and
Greetings Chris
EDIT
Maybe some info. I'm running
Windows 10 Pro (V10.0.15063)
and a basic network setup with a router and DHCP
I had the same problem today.
When I type
heroku
in my Command Prompt, it promotes me to enter my email and after that my password. Then I got the same error message as you.
After that instead "heroku" I typed
heroku login
I entered the same email and password and everything was fine.
Ok. I made it work. Unfortunately I'm not really understanding why this worked which is pretty unsatisfying but I'll tell you what I did. I stumbled on some posts that were saying heroku-cli is outdated if that happens. First I tried to update it with npm using
npm update -g heroku-cli
which basically made heroku stop working alltogether because now the cli reported it needed node >7.X (and I was still running on 6.X). The node update I then made also didn't help because now heroku-cli was unable find the command bash.
In the end I just reinstalled heroku. After that (with at first getting the same error as in the beginning) I first did
heroku update
and after that heroku login worked. Now why I don't really grasp and maybe someone of you guys knows. But the version I had before heroku update was exaclty the same as afterwards
heroku-cli/5.11.12-8ae9780 (windows-amd64) go1.7.5
I found out the heroku.cl was blocked by my antivirus and unblocked it. Now its working flawless.
Updating Heroku worked for me.
heroku update
I tried to use scrapy to scrap one website but kept receiving the error "Connection to the other side was lost in a non-clean fashion."
Tried to set the user agent and headers but it won't work. The following is the completed log. Any idea will be apprieciated.
http://pastebin.com/CSQ7Dkme
I think the reason for this information is that there is a problem with the requested page, not the code.
We've got an instance of Magento developed (two, in fact, since we tested both 1.6 and 1.7), and we are unable to have stamps.com hit its API. I've checked all the logs in our reverse proxy as well as Apache, and the connection is made, is successful, and it closes OK — so nothing's getting blocked. However, the API call times out, and we get this error when it hits the ShippingZmagento.php:
<Error>
<Code>1</Code>
<Description>Please, make sure that you use right URL. Url is case sensitive</Description>
<MessageDetails>http://mysubdomain.mydomain.com/index.php/api/soap/?wsdl</MessageDetails>
<Version>3.0.0.55618</Version>
</Error>
The FQDN is correct, and I'm about to hit the WSDL directly just fine as well — so it seems like a bad address translation might be happening at the API level or something.
We've tried it out in the DMZ with a couple of test domains (both with domains and subdomains), to no avail.
Any thoughts any of you might be able to shine on this would be most appreciated. Thanks in advance!
Open up stamps.com's php files and search for wsdl references they will need to updated to work on 1.7 magento:
What is SOAP V2 url on Magento 1.7.0.0