Skip to Content
This question has been flagged
domainec2v17
2 Replies
1943 Zobrazenia
Avatar
Alaa Albrg

After purchasing a domain through Namecheap, creating an Elastic IP on EC2, and adding a new inbound rule for port 8069 in the security settings, I continue to encounter the error message 'This site can’t be reached' when attempting to visit the domain (That I purchased from Namecheap). These updates were implemented last week.
Considering that I'm able to access Odoo using the Elastic IP and the specified port...
IP:Port ==> is working fine but when calling the domain via browser causing the issue. 

Any overlooked steps or recommendations for resolving this issue?

Avatar
Zrušiť
Avatar
Alaa Albrg
Autor Best Answer

Thank you, Niyas Raphy, for your assistance. I've observed that it functions when I input my domain along with port 8069 (mydomain. com: 8069). However, my concern arises from the fact that I'm utilizing Odoo 17, and it's less than ideal for users to manually input the port. What course of action do you recommend?

Avatar
Zrušiť
Avatar
Niyas Raphy (Walnut Software Solutions)
Best Answer

Hi,
Did you point the domain name to this iP address by adjusting the DNS set up of the domain name provider, if not you have to do it.

How To Configure Domain Name For Odoo Instance || Odoo Deployment

Thanks

Avatar
Zrušiť
Related Posts Replies Zobrazenia Aktivita
Need help with domain in Many2one field
domain pyhton v17
Avatar
Avatar
Avatar
3
aug 24
6010
'RequestHandler' object has no attribute 'headers'
ec2 odoo v17 17.0
Avatar
Avatar
1
jún 24
3389
domain with current user's company id in action(ir.actions.act_window) odoo17
domain custom domain_filter Domain v17
Avatar
Avatar
Avatar
2
júl 25
1758
naked domain set up Solved
domain
Avatar
Avatar
Avatar
Avatar
3
júl 25
4198
How to get the active_id from get_view function in odoo 17?
v17
Avatar
Avatar
Avatar
Avatar
Avatar
4
máj 25
2539