-
-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't connect to an AWS-hosted server #3
Comments
Hi @alexmasolin , |
Hello Hirotaka! Thank you for the super-quick support. What I know is that my server (the domain where the server is allocated) is using "Comodo EssentialSSL SHA-2 certificate" and you can find the root and intermediate certificates here: https://support.comodo.com/index.php?/comodo/Knowledgebase/Article/View/620/0/ From this page you can download several files like: but, due to my lack of knowledge, I wasn't able to know which one is needed in the script. Can you help me? If I browse from Chrome of course I get a 204 reply from the server. You can try your self with the following GET: https:// earthangel -28c4556f .influxcloud.net: 8086/ping Many thanks in advance |
Hi @alexmasolin , Maybe your Photon firmware is not 0.6.3? Please use 0.6.3(default) firmware. |
Hello @hirotakaster I was aware about the problems with 0.7.x and 0.8.x so I sticked with 0.6.3 firmware. Cheers, |
Hi @alexmasolin , Okay!! I got a same error on your server. I would test with COMODO root ca with your server okay? |
Hey @hirotakaster Cheers, |
Hi @alexmasolin , All problem is clear but not resolved(sorry...). The point of the problems is Photon memory limitation. here is my test.
I try to clear this problem but it need a time. Thank you |
Hi @hirotakaster Changing certificate would be a nice -to-have... unfortunately we use influx cloud services so the server is managed directly by them.... I will try to ask them to change certificate but I'm not really positive. I suppose that you are already aware of this document: https://tls.mbed.org/kb/how-to/reduce-mbedtls-memory-and-storage-footprint Keep me posted. Cheers, |
Hi @alexmasolin , I can success to your COMODO certificate AWS, the previous post was my mistake.
Regards |
Dear @hirotakaster well... it works!!! You made my day :) I was able to get a positive response (a 204 not a 404) from the server by changing the buffer to Now I have to find a way to send the payload. I hope that, when I will integrate your library into my original script, I won't hit memory boundaries. Did you follow some advice about memory footprint reduction? See #3 (comment) Once again, thank you very very much! Lot of luck |
Hi @alexmasolin , okay, that's good.
Thank you, I tried to use mbedTLS memory Reduce and Footprint with EEPROM and SRAM in the past but I get a two problem.
Now application could use about 16Kbyte free memory area with this library and sample source. Thank you, |
Hello @hirotakaster Few thoughts about memory reduction:
Using System.freeMemory() gives me 5400bytes available... not much... if I increase the buff size to 512 I get an SOS with 1 blink (Hard fault). Finally - most important - I'm struggling to send a body with my post request. I've tried so many ways.... could you please give me a working example? POST /write?db=mydb&u=user&p=password HTTP/1.1 power,system=one value=1234 I've tried to use this line in your application Many thanks, |
Hi, @alexmasolin , here is sample with my webbserver.
server side PHP is very simple.
In the Particle community site developer reported how to manage the memory, but I don't sure this option is correct or not(I think maybe some case would be good but others don't). And please use version 0.2.10. This version is light the memory about 2kbyte compare to 0.2.9. Thank you |
Awesome! Everything is fixed! |
Hello Hirotaka!
Great work with this library!!!
I would like to connect my Particle Photon directly to my database (InfluxDb instance on AWS cloud). The database is behind the AWS load balancer using default security policy.
My idea is to post a value directly from the Photon via an HTTPS post.
Unfortunately, I can't make it working: there is no "invalid certificate" or other errors. I was able to pin-point that the issue could be non compatibility of the ciphers used.
The ciphers supported by AWS are the following: https://docs.aws.amazon.com/elasticloadbalancing/latest/classic/elb-ssl-security-policy.html#ssl-ciphers
Could you please address this issue?
Thanks in advance,
Alex Masolin
The text was updated successfully, but these errors were encountered: