The warning message is an indicator that something is wrong. Can you go to Image Info tab of the camera INDI Control Panel and check that out? also the mount module, what's the focal length listed there?
The only thing remaining that would be possible is language and different between decimal point and comma, but that'd hardly an issue now as it was addressed long ago. But I'm running out of ideas and this is the only thing that would explains it.
Note that I trimmed the area when I captured an image but neglected to do reflect that in the scaling options. I don't know if that had a deleterious effect.
Also, I ran solve-field on the remote computer, blind, without any options at all. Although I didn't record how long it took to solve, it was quite rapid. So I wonder if running the solver remotely created some kind of bottleneck.
There also seemed to be a problem with solving to coordinates for which Ekos had no object. Thus, for example, I tried solving to a star dimmer than 8.4, but the solver solved to a near by brighter star. But I'll investigate further and post separately if it continues to be a problem.
I ran your fits file too, and like you got slow results with astrometry, but got virtually instant results from ASTAP (inside of EKos).
Why not install and use the ASTAP option (either permanently or until this gets worked out)?
You do need to install ASTAP to do that. www.hnsky.org/astap.htm
I did play with the file that was linked (light23.fits).
After setting the telescope simulator location to Wega and doing an inital solve with "use scale OFF", Ekos calculated a focal length of 521.7mm (I should add that I used my CCD simulator config with 4144x2822 pixels of 4.63qm size resembling the ASI 294). After this
ASTAP solved in 0.6 seconds (use scale ON),
local astrometry solved in 15 seconds (use scale ON) and
the internal solver solved in 4.4 seconds (use scale ON).
All with builtin method for solver and default options profile.
The internal solver first reported 0 stars found in the picture. Initially it detected enough stars but after applying filters, 0 stars remained. I then set minimum star size to 1 pixel (instead of 8, dont know whether that was one of my previous modifications) and this did the trick.
I used an older laptop with 4GB ram and an Intel firstname.lastname@example.orgGHz.
I have been having the same issue getting solver to work and also see the polar alignment disable message.
Bringing up a new configuration having updated to the recent stable release. Redcat 51 scope and ASI294 camera. FOV: 264'x180'
After doing the following two things the solver started working but the polar alignment message was still there.
First I had 6 configurations defined as seen in the telescope indi panel under the options tab and deleted them all except the RedCat one.
Second and this is probably not generally useful. The ASI294 has two modes of operation.
2.32µm 8288x5644 22M (bin1 14K Full Well, 12bit ADC)
4.64µm 4144x2822 11M (bin2 66K Full Well, 14bit ADC)
I had made the mistake of deciding to use bin2 and setting up Ekos using those values. Instead changed all the values to the first mode. Then used the bin setting on the various screens as usual.
After making the changes it solved using [ bin1 and ] the internal guider for the first time various targets with good response times.
Lost the weather at that point so will see if it holds up next time.
I'm wondering about ASTAP. Does one need the full suite to run the solver under Ekos/indiserver? I notice there is an ASTAP-CLI package in the Debian repository.
Also, I wonder how the ASTAP database, H18, gets by with less than 1 gigabyte when the astrometry.net data files for my setup take up 32 gigabytes. From the ASTAP website, H18 includes stars down to 18th magnitude.