@dan said in How can I make sure FusionAuth is running when I start it via docker-compose?:

It's not responding at the port 9011, like it should.
Is there a way to test or ping the FusionAuth App to make sure its up and running other than using docker ps -a?

Yes, there are several ways to test or ping the FusionAuth App to check if it's up and running without relying on the docker ps -a command. Here are a few alternative methods:

Curl or wget: You can use the curl or wget command-line tools to send a request to the FusionAuth App's endpoint and check the response. For example, you can run curl http://localhost:9011 or wget http://localhost:9011 to send a GET request to the FusionAuth App running on port 9011. If you receive a valid response, it indicates that the app is up and running.

Telnet: You can use the telnet command to establish a connection to the FusionAuth App's port and check if it's open and responsive. Run telnet localhost 9011 to attempt a connection to the FusionAuth App on port 9011. If the connection is successful, it means the app is running and accepting connections.

Browser access: Simply open a web browser and enter the URL http://localhost:9011 to access the FusionAuth App. If the app is running correctly, you should be able to see the login or landing page.

API client: If the FusionAuth App provides an API, you can use an API client like Postman or cURL to send a request to the API endpoints and verify if you receive the expected responses.

These methods allow you to test the availability and responsiveness of the FusionAuth App without relying on the docker ps -a command or using Docker-specific tools.

Hello, Time unit difference: The timestamps may be stored or represented in different units. For example, one library might use seconds while the other uses milliseconds. This can result in significantly different values for the expiration date.

Timezone handling: The libraries may handle timezones differently, which can affect the calculated expiration date. Make sure that the libraries are using the same timezone or that any necessary conversions are being applied consistently.

Timestamp format: The libraries might use different formats to store or interpret timestamps. Check if the libraries expect timestamps in a specific format and ensure that they are being provided correctly when generating or validating the JWT.

To resolve the issue, you can try the following steps:

Review library documentation: Check the documentation of both the .NET Core and Java client libraries for any specific information regarding timestamp handling, timezone considerations, or timestamp formats.

Verify input values: Ensure that the input values provided to both libraries are consistent and correctly represent the expiration timestamp. Double-check any conversion or formatting steps involved.

Test with sample data: Create a test case with sample data and compare the outputs of both libraries to identify any discrepancies or patterns.

Consult library support or community: If the issue persists, consider reaching out to the library maintainers or their respective communities for further assistance. They may be able to provide insights or suggest specific solutions for your scenario.

If a user is still receiving a SearchEngineRequestFailedException after a system reindex and patching, there could be several reasons for this.

Firstly, the issue may not have been related to the index or patching, but rather a problem with the user's search query or the way they are interacting with the system.

Alternatively, it could be that the reindex and patching process did not fully resolve the underlying issue, and further investigation or troubleshooting is necessary.

It's also possible that there are other technical or environmental factors at play that are causing the exception to continue occurring. In any case, it may be necessary to consult with technical support or seek out additional resources to diagnose and resolve the issue.