Hi @przegee I'm not sure what's going on here... but yes, the unusual port 8000 might be the problem. I'll do some digging and give you an updated.
Thank you @steveatsafe for response. I used another instance of FME, installed on remote machine, and after fixing CORE domains, I managed to connect to rest api. However, I was anabled to send queries from ajax method itself, but using FMEServer.js helps and now I can reach FMERest from my service.
Cheers
Thank you @steveatsafe for response. I used another instance of FME, installed on remote machine, and after fixing CORE domains, I managed to connect to rest api. However, I was anabled to send queries from ajax method itself, but using FMEServer.js helps and now I can reach FMERest from my service.
Cheers
Hi @przegee,
I'm curious after you configured CORS did you restart FMEServer?
Our developer had this to say "manual restart of server should cause the changes to take effect."
Thank you @steveatsafe for response. I used another instance of FME, installed on remote machine, and after fixing CORE domains, I managed to connect to rest api. However, I was anabled to send queries from ajax method itself, but using FMEServer.js helps and now I can reach FMERest from my service.
Cheers
@steveatsafe, no, there's no need to restart FME after changing CORE policy. I do it quite often and it reacts quickly.
@steveatsafe, no, there's no need to restart FME after changing CORE policy. I do it quite often and it reacts quickly.
Hi @przegee, Interesting that you find that. Let me speak with our Developer again and confirm why that was suggested? Perhaps I misunderstood and he meant the System was to be restarted.
Hi @przegee
I spoke with our Developer Rob on this... he's shared this with me. I hope it clarifies some things that I wasn't clear about when I first responded to you as my understanding wasn't complete.
"When you change CORS settings the webUI backend contacts the other services and tells them to reload. It contacts them by using the URL definitions in the Services configuration view. in this case he was trying to contact https://localhost/fmerest according to his screenshots.
The other screenshot shows the connection was refused and the REST service did not receive the message to change it's CORS settings. Why? I can't tell. Were all the services returning an error or just the ones showing? Was there some firewall rule? Was the other services not running? Was his SSL certificate invalid and couldn't be used in this automated process.
... But an error is OK. If you get an error, it means the CORS settings couldn't be updated on the fly.
Restarting FME Server will start the services back up and they will honour the new CORS setting."
I hope this helps you investigate further and resolve the issue...
