0

I've tried running my yaws Web-server (on digital-ocean) by changing my webpage from http://XXX.XX.XX to https://XXX.XX.XX

on the Erlang shell, i get 

SSL accept failed: {tls_alert, "decode error"}

the yaws.conf seems to come with a default key and certificate and i haven't made any modifications to that.

could i check what needs to be done to enable SSL? thanks much.

user3847136
  • 47
  • 1
  • 6
  • 1
    Can you maybe post some debug information, e.g.: `curl -v --trace-time --trace-ascii server1.log https://XXX.XX.XX` – Greg Mar 01 '16 at 11:51
  • 1
    It would also help to provide version information for both Yaws and Erlang, and also show your `yaws.conf`, especially the part for the server under which the error occurs. – Steve Vinoski Mar 01 '16 at 12:15
  • 1
    Do the default key and cert actually exist? Or does the configuration mention some files as examples, but the files don't really exist? – Nathaniel Waisbrot Mar 02 '16 at 19:11
  • @Amiramix thank you very much. I traced your steps and figured out that it was a problem with my openssl settings. Thereafter I followed the responses to other SO questions and solved it. – user3847136 Mar 03 '16 at 21:59
  • @SteveVinoski thank you for your response. I used the latest versions and example yaws.conf codes. Those were ok, the problem was with my openssl code as articulated above. The trace logs were immensely helpful. – user3847136 Mar 03 '16 at 22:00
  • @NathanielWaisbrot thanks. Yes the files really existed, but those were not tied to the particular server. So following the traces helped figure out what was wrong. – user3847136 Mar 03 '16 at 22:00
  • @user3847136: if there are other SO questions that answered your question, we should mark this as a duplicate of the best one of those. – Steve Vinoski Mar 03 '16 at 22:04

1 Answers1

0

Following the suggestion of Amiramix to check the trace via

curl -v --trace-time --trace-ascii server1.log https://XXX.XX.XX

solved the question.

user3847136
  • 47
  • 1
  • 6