Nope, got a new error now.
curl: (51) SSL: no alternative certificate subject name matches target host name ‘10.10.2.188’
cant i use my external dns adress instead ?
Interesting, try adding a -k option to the curl command. That means ignore SSL errors or something like that.
where in the command should i add -K
/usr/sbin/arp -a > /root/arp.tmp && /usr/local/bin/curl -X POST -F ‘data=@/root/arp.tmp’ https://10.10.2.188:8123/api/pfsense
/usr/sbin/arp -a > /root/arp.tmp && /usr/local/bin/curl -k -X POST -F ‘data=@/root/arp.tmp’ https://10.10.2.188:8123/api/pfsense
Get this back
curl: (6) Could not resolve host:
Well that’s confusing. Can you ping 10.10.2.188 from the pfsense terminal?
Hmmmm okay I’ll try this with SSL and see what happens. I’ll report back.
1 Like
Can you send me the your “arp.tmp” file? I wonder if it is formatted differently than mine.
Had to add .yaml to be able to upload
Hmm it seems okay. I’ll try sending it through on my system and see what happens.
probably works right?
Yeah worked fine. The command in the screenshot above doesn’t look correct.
Looks like you are sending data=@/root/
It should be 'data=@/root/arp.tmp' You have to have the single ' around the data= part
what does this mean
curl: (52) Empty reply from server
That looks fine too.
can you try running this command from pfsense?
curl -k -X GET -H "x-ha-access: YOUR_HA_PASSWORD" -H "Content-Type: application/json" https://10.10.2.188:8123/api/
It should respond with
{"message": "API running."}
This is a base functionality that HA has, so if it doesn’t work there is something unrelated to what we are trying causing the problem.
That means it sent a request, but the server didn’t respond with anything at all. That is a violation of the http protocol. It should always respond with something. So most likely it isn’t getting where it wants to get.