wrong entry point generated for staticman self-hosted

[bschwand]

I had staticman comments working on a blog with minimal mistakes, hosting staticman on heroku, but for various reasons I want to self-host staticman.
I set it up and tested it works as I can test submitting a comment with wget like this
wget -d --post-data='fields[name]=burno&fields[email]=brunotinkerborg&fields[message]=this_is_a_message' http://<myhost.domain.com>:8088/v3/entry/github/bschwand/bschwand.github.io/gh-pages/comments
note that I am running staticman on a separate port (8088) and not over https.
Now, I enabled staticman endpoint in _config.yml like this

  staticman:
    branch               : "gh-pages" # "master"
    endpoint             : "http://>myhostname.domain.com>:8088/v3/entry/github/"

but when I go to my page and submit a comment, it fails everytime giving the message that something went wrong.

Looking in my browser with the developer tools, I see that the request to staticman timed out. That makes no sense as my server is definitely up and running. It looks like it is never contacted at all. So I wonder if the endpoint url can not be on a separate port and non-https ?
Second thing I notice is that in the browser log again, the endpoint that it is submitting the comment to is like this
http://<myhost.domain.com>:8088/v3/entry/githubbschwand/bschwand.github.io/gh-pages/comments
notice the absence of '/' between github and the username (bschwand)

and yes, I tried to set the endpoint in _config.yml with 2 '/' at the end just to see and in that case the url ends up being
http://<myhost.domain.com>:8088/v3/entry/github//bschwand/bschwand.github.io/gh-pages/comments

in both urls' if I test them manually with wget, I get an error response, so I know my staticman instance is working. But from the browser, trying to submit a comment, it times out.

So, seems two issues, maybe coming from the same one:

• I have a special port (8088) and not running on https.
• But there might also be a bug in how the endpoint url is constructed and used

I must say I am not familiar with minimal mistakes codebase and actually how it all works together (like where in the code is the endpoint url constructed and submitted ?)

Eventually, I'll setup a https proxy on my staticman instance, but that is yet another layer and bag of possible issues, so I'd like to validate it all works first before adding encryption.

Anyway, if anybody has some idea about what is going on, or which part of the code to look at, comments appreciated.
cheers

[bschwand]

solved the issue. not sure why I was seeing an incorrect entry point, but by configuring nginx as SSL proxy in front of staticman, and setting the correct https entrypoint url, now comments work.