- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
What do you mean by "cannot see the service in my domain"?
The documentation describes the steps to change the instance type [1]. If the instance starts and you can connect via SSH for instance, I would recommend to troubleshoot the service itself in the OS.
Also, are you using the public IP to access the service? If so, if you do not attach an elastic IP to the instance, the IP will change once you stop and start the instance.
Finally, as per the Passbolt documentation [2], t2.micro does not seem to match the vendor minimum hardware requirements (2 cores, 2Gb RAM).
Hope that helps.
[1] https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-resize.html
[2] https://help.passbolt.com/faq/hosting/hosting-requirements
I attempted to change the instance type from medium to micro. Because of your comment i set back to the medium instance again.... do you happen to know how to see my passbolt again? The IP has changed and the page where I used to see my passbolt fails at the moment.
Relevanter Inhalt
AWS OFFICIALAktualisiert vor einem Jahr- AWS OFFICIALAktualisiert vor 3 Jahren
- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor einem Jahr
Hey, If the IP changed, I would recommend you to use the command "dpkg-reconfigure passbolt-pro-server" (change pro by ce in the command depending on the Passbolt version you use) -> answer "no" for the mysql part -> answer "yes" for the nginx server then choose the same option you did the first time (none or manual or auto) and here you will be able to chain the Passbolt domain name, you can put your new IP and then get back to your browser to access back to your Passbolt instance via the new IP/Domain name. As mentioned before, I would strongly recommend you to attach an elastic IP to your instance in order to not have to reconfigure this every time it restarts. https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/elastic-ip-addresses-eip.html