Hello there, again. I am a Laravel dev and was wondering if I can make a domain or subdomain in InfinityFree point at a certain directory in your project (e.g. the home directory for my domain example.com is “myaccount/example.com/public/” but apparently it only supports the htdocs) so I tried to do something like this:
so I have an index file in “htdocs” that points at the application core in “core” (which is outside of the htdocs that was associated to this specific domain), It did work when I had it set up but now it doesn’t and if you visit this domain that was working for the first day, it doesn’t now
so my question is, Is my account restricted or something because I did this or did something go wrong or is there a configuration missing, if restricted — is there a way to make a domain like this point at a certian directory or this is overkill for a free shared hosting plan like IF’s?
Alright regardless of this, I have a simple <?php echo “123”; index.php page in the htdocs of my domain (http://playpal.great-site.net/) and it shows this error:
I’m not sure if this is because I uploaded files outside the htdocs earlier or what exactly the issue is, could my account be restricted by InfinityFree without a notice, an email or a mark on my InfinifyFree’s dashboard?
You’re experiencing a different issue than you think, possibly the great-site.net domain being blocked by your ISP.
If you had done something that was actually against the TOS you’d be suspended which would result in your site redirecting to the official suspension page. It wouldn’t cause a random timeout error.
It’s not supposed to work. PHP code on websites is supposed to only be able to access files within the htdocs folder of that website. If it was possible, then that must have been a temporary issue that has now been fixed.
So to fix this, you’ll need to move the core folder within the htdocs folder to be able to use it.
The connection timed out error is a network issue. It’s because you are blocked from accessing our servers, either by us or by something on your end (like a firewall, antivirus or other security filter).
It’s not an account level restriction, and it’s not caused by anything you did on your website.
Update: the connection timed out error was a block on our end. Your IP address (or rather the network your IP address belongs to) was blocked due to abnormal traffic. This block has now been lifted, so you should be able to access your site again now.
)