RDP is up and running still message is not redirected to the consumer.

I would guess that there is just some settings with VirtualBox networking that needs to be resolved.

Let’s do tests step by step:

  1. Make sure the REST API is accessible from your Windows host itself. You can use curl from WSL or simply open 192.168.1.6:9090 from your browser. With Chrome you can run Inspect and make sure you get HTTP 200 OK.
  2. If that works, let’s test from within Solace PubSub+ container. First just check if we can ping 192.168.1.6 from your Solace shell.
  3. If that works, let’s check the REST port. You can test this by doing curl -v 192.168.1.6:9090 from your Solace shell, just to easily check the connection is there or not.
  4. If that works too, then we need to look at your Solace logs to check :slight_smile:

Otherwise you could play around with the Solace Cloud free instance and point out to a dummy REST API server on Internet like http://dummy.restapiexample.com to avoid the networking hassles. For free Solace Cloud instances, just go to console.solace.cloud and create a user.

Hi Ari,
Please find screenshot of stats below.

  1. REST API is accessible from host and able to get HTTP 200 OK
  2. Able to ping 192.168.1.6 from solace shell.
  3. curl -v 192.168.1.6:9090 from Solace shell is failing, Connection timed out.

I have also created a cloud account. what port we can give in consumer while using http://dummy.restapiexample.com?

Thanks & Regards,
Saurabh

Hi @Saurabh ,

Well we see that there is a connectivity issue here, that’s why we still can’t get the REST consumer to run. I’m not sure why, but maybe worthwhile to check on your Windows firewall settings.

If you’re testing with a test REST API service, I found out that it might be easier to use postman-echo.com and port 80 for this. And don’t forget to change the POST Request Target from /rest/tutorials to /post