its got the right permission and chmod, so this is baffling
tired both with the api user and my full access user and same result each time
now I have no working webhooks as the server has been moved over to the new one at DNS level
actually cant create any API key as it refuses to open any file with my user:pass
Otto 4.5 in 21.0.2.202 on Ubuntu 22.04
Can you open the file with FileMaker Pro?
Is the Data Api Running?
Todd
Opens with Pro, new SSL is all installed properly, have turned off and turned back on DAPI, and in the process there has been a server reboot too…
How about the logs?
FileNames with different case then on the other server?
Todd
Haven’t tried to move webhooks over yet, was just trying to test that all works as expected
I copied my OttoHook file from server A to server B, set permissions etc
Have done things like open and close files, and set up an Admin API key
Tried to set up a dataapi key and it resolutely refuses…
And the only Otto log with anything in is the Otto-info and its so new that there’s only about 30 lines in it and all looks good.
Check the FileMaker logs. Does it show anything about the attempt to open the file?
Did you move from Windows to Linux? FileName case sensitively is different on the different platform and has bitten me a few times.
Todd
no linux to linux
No attempt to connect in Event or Access log…
just tried on a totally different server I know has similar spec and all works
created a brand new file and uploaded to this new one, also refuses to open
Can you try connecting to the Data API via postman?
and oh are you sure you have the right DNS resolving. I have been bit by that too… I think I am hitting Server A and I am hitting Server B
Todd
I am pretty sure I was but that’s something else to check
Will have to come back to it tomorrow as I need some overnight things to run and they need it first thing and I can’t miss more webhooks so changed it all back
Update with the benefit of sleep and sunshine
The file does not open from Postman : 802 error, turned off DAPI and get a bad gateway instead.
No other file will open using DAPI from Postman
Checked firewall both local and instance
uninstall FMS, reboot, install 21.0.1
open brand new test file, refuses to open with DAPI
OK
solved by completely trashing the instance and installing all from scratch, with all the extra personalisations for this application
First thing was to copy receiver file and check it could be reach by DAPI from Postman, tick
Copied the db.sqlite and rconf as per other thread and all is theoretically working, just need to wait tiil after-hours to copy all live files (cant use OttoDeploy as the same fqdn is being swapped over)
