wildcard subdomain issue on Plesk panel

I have deployed my nuxt app on my Hostiner vps using plesk panel, I can access the app on "example.com" but when I try to access the subdomain that points to the app root directory as the main domain I get 403 page error, I have created a DNS A record *.example.com points to my server ip, and I also have created a wildcard subdomain on plesk panel but when I try to access any subdomain I get the 403 page error, any help, I have searched and asked ChatGPT but I couldn't find any solution, thanks
2 Replies
kapa.ai
kapa.ai2mo ago
Hi @devahmedadli. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave: ---------------------- I'm sorry, but the knowledge sources do not contain specific information about resolving wildcard subdomain (e.g., *.example.com) 403 errors for a Nuxt app deployed on a Hostinger VPS using Plesk Panel. There are references to 403 and 404 errors in the context of static hosting and custom error pages on Hostinger, but not about wildcard subdomain configuration or Plesk-specific setup. However, one related issue discussed is that on Hostinger, custom error pages (like 404) may need to be configured directly in the hosting control panel to avoid default hosting provider error pages. For 404 errors, editing the error page in the Hostinger dashboard and saving an empty HTML file resolved the issue for some users, but this does not directly address 403 errors or wildcard subdomains. There is no mention of Plesk-specific configuration or wildcard subdomain handling in the provided sources Why does my Nuxt application redirect to my hosting provider's 404 page and not my custom error.vue page?. If you need further help, you may want to check your Plesk and web server (e.g., Nginx or Apache) configuration to ensure that wildcard subdomains are correctly routed to your Nuxt app and that file/folder permissions are set properly. But unfortunately, the knowledge sources do not provide a step-by-step solution for this scenario. ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ----------------------
kapa.ai
kapa.ai2mo ago
<@1351510427179290624> Kapa.ai is still learning and improving, please let me know how I did by reacting below.

Did you find this page helpful?