Project LOGGED v2.0 - Free Login and Signup Form Template [2023 Update]

[MeTooIDK]

33 minutes ago, Aqib said:

All versions of WHMCS support MOFH.

But i see a video say WHMCS 7 DIDNT SUPPORT MOFH

[AA22Dev]

1 minute ago, MeTooIDK said:

But i see a video say WHMCS 7 DIDNT SUPPORT MOFH

I had made a video in which I used latest whmcs version at that time. Currently my site is down due to server migration but you might be able to read guide https://aavidtutorials.com/mofh/how-to-setup-whmcs-with-myownfreehost/ here because of cloudflare always online service.

Edited March 1, 2021 by Aqib

[MeTooIDK]

On 3/1/2021 at 12:55 PM, Aqib said:

I had made a video in which I used latest whmcs version at that time. Currently my site is down due to server migration but you might be able to read guide https://aavidtutorials.com/mofh/how-to-setup-whmcs-with-myownfreehost/ here because of cloudflare always online service.

Error 522
 Ray ID: [REDACTED]

Connection timed out

aavidtutorials.com

The initial connection between Cloudflare's network and the origin web server timed out. As a result, the web page can not be displayed.

 

[MeTooIDK]

1 hour ago, Aqib said:

I had made a video in which I used latest whmcs version at that time. Currently my site is down due to server migration but you might be able to read guide https://aavidtutorials.com/mofh/how-to-setup-whmcs-with-myownfreehost/ here because of cloudflare always online service.

I CAN SEE GUILD ON WAY BACK MACHINE

[AA22Dev]

28 minutes ago, MeTooIDK said:

Error 522

 Ray ID: 629229d16d090e76 • 2021-03-01 11:49:41 UTC

Connection timed out

 

You

Browser

Working

 

Tokyo

Cloudflare

Working

 

aavidtutorials.com

Host

Error

What happened?

The initial connection between Cloudflare's network and the origin web server timed out. As a result, the web page can not be displayed.

What can I do?

If you're a visitor of this website:

Please try again in a few minutes.

If you're the owner of this website:

Contact your hosting provider letting them know your web server is not completing requests. An Error 522 means that the request was able to connect to your web server, but that the request didn't finish. The most likely cause is that something on your server is hogging resources. Additional troubleshooting information here.

It might be because of server migration

[MeTooIDK]

Just now, Aqib said:

It might be because of server migration

i download that video.

[Ostad Fardeen]

Excellent! But can you add custom domain feature to next update so that users can sign up with their own custom domain?

[PlanetCloud]

6 minutes ago, Ostad Fardeen said:

Excellent! But can you add custom domain feature to next update so that users can sign up with their own custom domain?

Yes, will be considered on future version. Kindly advise the user to use any subdomain, and then add their custom domain afterwards through the cPanel.

[TinkerMan]

@PlanetCloud, you can get the basic code needed to validate domain names from MOFHY, just take care not to copy anything it it has become kind of famous for.

[PlanetCloud]

34 minutes ago, TinkerMan said:

@PlanetCloud, you can get the basic code needed to validate domain names from MOFHY, just take care not to copy anything it it has become kind of famous for.

What do you mean validate domain names?

[TinkerMan]

You have to send the custom domain to the MOFH API so the nameservers can be checked.

 

See: https://github.com/InfinityFreeHosting/mofh-client

• availability
  • domain: The domain name or subdomain to check.

 

	$client = Client::create();
	$request = $client->availability(['domain' => $FormData['domain']]);
	$response = $request->send();
	if($response->isSuccessful()==0&&strlen($response->getMessage())>1){
		//Something went wrong, display error message
		echo $response->getMessage();
		exit;
	}
	elseif($response->isSuccessful()==1&&$response->getMessage()==1){
		//The domain name can be used!
		echo $FormData['domain'];
		exit;
	}
	elseif($response->isSuccessful()==0&&$response->getMessage()==0){
		//Domain is already in use
		echo 'Sorry! domain name already registered';
		exit;
	}

 

[PlanetCloud]

6 hours ago, TinkerMan said:

You have to send the custom domain to the MOFH API so the nameservers can be checked.

 

See: https://github.com/InfinityFreeHosting/mofh-client

• availability
  • domain: The domain name or subdomain to check.

 

	$client = Client::create();
	$request = $client->availability(['domain' => $FormData['domain']]);
	$response = $request->send();
	if($response->isSuccessful()==0&&strlen($response->getMessage())>1){
		//Something went wrong, display error message
		echo $response->getMessage();
		exit;
	}
	elseif($response->isSuccessful()==1&&$response->getMessage()==1){
		//The domain name can be used!
		echo $FormData['domain'];
		exit;
	}
	elseif($response->isSuccessful()==0&&$response->getMessage()==0){
		//Domain is already in use
		echo 'Sorry! domain name already registered';
		exit;
	}

 

Ah... that's what you meant... well I have another way of handling that and also Project LOGGED (v1.x) is not meant to have anything to do with composer (yet).. I'll consider it though. I'm not sure will the inode limits be enough or how it will perform. Will have to do some testing.

[PlanetCloud]

I'd like to point out that there's an issue with the domain availability API where if the account is being created but not activated yet, the domain can still be registered, as seen in the screenshot below:

Both have the same main domain under different account. So you should not rely on MOFH API alone.

# Check domain availability
$domains = $db->select('accounts', 'id', ['main_domain' => $main_domain]);
if (count($domains) > 0) {
    throw new Rejection('Domain is not available.');
}
$response = MofhClient::availability($main_domain);
if (!$response->isSuccessful()) {
    throw new Rejection('Domain is not available.');
}

Here is my implementation to check the domain's availability. Please note that I make my own wrapper (MofhClient) to handle the errors that may be returned by the API. The errors are logged and will not be shown to the end user unless the DEBUG mode is enabled in the config.

[TinkerMan]

11 hours ago, PlanetCloud said:

Both have the same main domain under different account. So you should not rely on MOFH API alone.

Oh, thats not good to hear for non-code users, I wouldn’t expect it to be a big deal though. In any case, thanks for the notice

[qwe]

I just deleted my post, no more questions for now.

Edited July 16, 2022 by qwe

[qwe]

I just deleted my post

Edited July 16, 2022 by qwe

[RoshanOp]

Hey there,

I unzipped the files in FreeWH.gq

But it's giving HTTP 500 errors.

link: https://FreeWH.gq/signup.php

Edited September 3, 2022 by RoshanOp

[Anyx]

6 hours ago, RoshanOp said:

Hey there,

I unzipped the files in FreeWH.gq

But it's giving HTTP 500 errors.

link: https://FreeWH.gq/signup.php

There seems to be a problem with your .htaccess configuration. Normally, https://freewh.gq/sys-auth/ should not be directly accessible, and you should get custom error pages.

Do your .htaccess files contain the rules present in Project LOGGED do by default (mainly https://github.com/PlanetTheCloud/project-logged/blob/master/.htaccess, and https://github.com/PlanetTheCloud/project-logged/blob/master/sys-auth/.htaccess)? Have you correctly followed the setup instructions in https://github.com/PlanetTheCloud/project-logged/wiki/Setup-Instruction-(1.8)?

Edited September 3, 2022 by Anyx

[RoshanOp]

23 hours ago, Anyx said:

There seems to be a problem with your .htaccess configuration. Normally, https://freewh.gq/sys-auth/ should not be directly accessible, and you should get custom error pages.

Do your .htaccess files contain the rules present in Project LOGGED do by default (mainly https://github.com/PlanetTheCloud/project-logged/blob/master/.htaccess, and https://github.com/PlanetTheCloud/project-logged/blob/master/sys-auth/.htaccess)? Have you correctly followed the setup instructions in https://github.com/PlanetTheCloud/project-logged/wiki/Setup-Instruction-(1.8)?

umm, it wasnt addded in sys-auth folder. but it was in the htdocs (main) folder.
still i updated both of them, cleared my cookies, and its been a while.
Still same issue

Edit: Also, for the auth folder (its listed in .htaccess above the sys-auth folder
But, in the repo, i dont see any /auth folder

Edited September 4, 2022 by RoshanOp
I forgot to add one thing

[Anyx]

1 hour ago, RoshanOp said:

umm, it wasnt addded in sys-auth folder. but it was in the htdocs (main) folder.
still i updated both of them, cleared my cookies, and its been a while.
Still same issue

Edit: Also, for the auth folder (its listed in .htaccess above the sys-auth folder
But, in the repo, i dont see any /auth folder

I'm not sure what you did right now, but I can't see either a home page or visit a login/auth page. Where did you put Project LOGGED in?

You can join LOGGED's Discord if you'd like, we may be able to help you better there.

EDIT: Nevermind, you're using Xera now. Good luck!

Edited September 4, 2022 by Anyx
Xera

[PlanetCloud]

This thread has been updated for LOGGED v2.0 and to maintain the pinned status.

However, it is recommended that replies about LOGGED v2.0 are made to it's own thread here:

Thank you.