-
Notifications
You must be signed in to change notification settings - Fork 461
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Maildev UI not opening in Browser #136
Comments
Hi @odidev. Thanks for your interest in the Pitstop sample application! I have fixed the version of MailDev to 1.1.0 because I had issues with the latest version (see commit 3cb01f5). So you should use 1.1.0 (and ports 25 and 80). I was not able to reproduce this issue on Ubuntu AMD64 (using WSL2!). Please double check the log output of the services to see whether all messages are being sent over RabbitMQ and the NotificationService and InvoiceService receive events after planning or completing a maintenance-job. Then send a |
Hi EdwinVW, Thanks for the quick response! I have followed your suggestion and tested the pitstop application with maildev v.1.10 and it is working fine for me. I have also worked on deploying the microservices on docker swarm although facing issue while running the webapp and related services as their state is failed/rejected/shutdown. Please have a look at the logs below:
Please find below the steps I used to deploy pitstop through docker swarm: -
Note: - I have used docker-compose.yml as my docker-swarm.yml file and modified it with these changes. It will be really helpful if you could share your pointers here to resolve the issue. |
Unfortunately, I have no experience with Docker Swarm. So I won't be able to really help you with the issue. The logging also doesn't provide enough information to determine what the issue is: If I had to guess what could be the issue, then I would look at what the Pitstop services do when they are started. They try to connect to SQL Server and RabbitMQ. Perhaps these containers took too long to come up. Although, the Pitstop services retry 10 times (with an interval of 5 seconds for RabbitMQ and 10 seconds for SQL Server). So that should be enough. So I'm sorry I can't be of more help to you. |
Hi @odidev. Can I close this issue? |
Hi EdwinVW, Thanks for your previous pointers, I have made progress with deploying pitstop through docker swarm. Please find below the steps for the same:
Note: - HEALTHCHECK doesn’t work with docker swarm that’s why needed to remove the same while deploying services through docker swarm. Now I am able to successfully deploy all the services through docker swarm. Please have a look at the logs: -
Although when trying to test the services in browser some services are showing as offline. Please have a look at the logs below: - It would be helpful if you could suggest some pointers on what might be the reason for the services being offline. |
The services are probably not offline, but the URI used to connect to them is probably not correct. Please check the following things:
I'm not familiar with Docker swarm, but I guess that the hostnames are |
Hi EdwinVW, Thanks for your suggestion. I have implemented the same, but all 3 services are still offline. I have checked adding networks in config file but no progress. Please do share if you have any other pointers. Thanks. |
I'm sorry @odidev, but I'm not able to help you any further (as I have no experience with Docker Swarm). |
Hi @odidev. Can I close this issue (as I'm not able to help you any further)? |
@EdwinVW Thanks for your previous input, it was helpful. I have been working on performance testing the pitstop application with locust.io on aws ec2 ubuntu arm64 instance. Please find below a detailed explanation of the same:
Please find below the steps to test the same:
After exploring the above issue, it seems like it is because of the Request verification Token that is being generated in the payload when we register a customer to the customer management portal. It would be really helpful if you could share pointers on this. Please share your thoughts on this. |
Hi @odidev. As stated, I'm not able to help you any further with this. So I will close the issue. |
Hi EdwinVW,
I have worked on running pitstop with docker-compose, Kubernetes etc on ubuntu arm64 and amd64 platform. Although it looks like with maildev image v1.2.0-beta1, the maildev UI doesn’t open while running through docker-compose.
I had to do below mentioned changes in
docker-compose.yml
post that only the web-page of Maildev opened.Also, with the above changes only UI of maildev gets opened in browser but I am not able to receive any email while testing for invoice and notifications.
Please find below the steps to reproduce the issue:
Please share your pointers as to how to resolve the same. Thanks in advance!
The text was updated successfully, but these errors were encountered: