Jump to content

Friends cant join my forge server using my public ip but i can join using my ipv4


Recommended Posts

6 hours ago, diesieben07 said:

You posted a screenshot of your server.properties with server-ip set. Do not set it.

so i just leave it blank?

but i need my ipv4 there so the server runs dont i?


Edited by itzdawid
Link to comment
Share on other sites

7 minutes ago, diesieben07 said:

You are running this server on your home internet connection, right? Normal home routers have a firewall and NAT (when using ipv4) built in, so that no connections can be made from the outside. You need to configure your router to allow people to connect to your server.

so i just disable my firewall?

coz if thats the problem im not sure how im ment to configure it properly


Link to comment
Share on other sites

Just now, diesieben07 said:

No, do not just disable it.

There are plenty of instructions on how to host your own server.

the thing is is that it worked yesturday but the mods wont loading now that i fixed that issue no1 can join my server anymore

Link to comment
Share on other sites

9 minutes ago, diesieben07 said:

Why are you just now providing this information?

Again: You need to post the debug.log (not some other log!) from your server and the client that cannot connect. You do not need to post screenshots or any other logs.

it doesn't let me post the debug.log it just says " -200 " and i still dont understand what you mean by client that cannot connect

image.png.c5a5615a5f3900df28e5ed44d13ebfb0.png thats what it says when i try to upload the log

Edited by itzdawid
Link to comment
Share on other sites

5 minutes ago, diesieben07 said:
  1. You can use https://gist.github.com/ or similar services to post large text files.
  2. The "client that cannot connect" is, well, the client that cannot connect to your server. You said there are multiple people trying to connect, but it does not work for them. Post either of their debug.log files as well.

https://gist.github.com/itzDawid/dd3c6e74db8fa380c90cff6dd80100a6 here is the link to the dubug and unfortunatly non of the poeple that are trying to join are currently online and arent able to come on at this time 

Link to comment
Share on other sites

1 minute ago, diesieben07 said:

From the log it looks like nobody is even attempting to join as far as the server is concerned. So yeah, we need those client logs.

can i just try and join using my public ip and just update the logs?

because i can join using my ipv4 but not my public ip

Edited by itzdawid
Link to comment
Share on other sites

2 minutes ago, diesieben07 said:

How is that going to help considering that already works...?

no lyk i did it earlier i am able to join using my ipv4 but when i use my public ip i am unable to join and get the same msg as my mates

Edited by itzdawid
Link to comment
Share on other sites

Just now, diesieben07 said:

This just screams that your router is not configured properly.

But you said it worked before... are you 100% about that?

yes i am 200% sure it worked before, but what specificaly do i have to configure in my router might aswell test some stuff 

Link to comment
Share on other sites

1 minute ago, diesieben07 said:

I am not going to explain to you how to configure your router.

This can in theory have security impacts. If you do not know what you are doing, you should not be touching these settings and just get a hosted server.

is there any other way then i could host a server or allow my friends to join my world? 

Link to comment
Share on other sites

  • 5 months later...
On 7/13/2019 at 7:50 PM, itzdawid said:

is there any other way then i could host a server or allow my friends to join my world? 

Yes, buy a pre-configured host or learn/inform yourself as to how port-forwarding works and how to prevent security compromises.


Perhaps if you still encounter this issue, I am more than happy to provide my competence to help you via PM

Link to comment
Share on other sites

If you just want to play with friends, Hamachi is a popular VPN for doing so

This is my Forum Signature, I am currently attempting to transform it into a small guide for fixing easier issues using spoiler blocks to keep things tidy.


As the most common issue I feel I should put this outside the main bulk:

The only official source for Forge is https://files.minecraftforge.net, and the only site I trust for getting mods is CurseForge.

If you use any site other than these, please take a look at the StopModReposts project and install their browser extension, I would also advise running a virus scan.


For players asking for assistance with Forge please expand the spoiler below and read the appropriate section(s) in its/their entirety.


Logs (Most issues require logs to diagnose):


Please post logs using one of the following sites (Thank you Lumber Wizard for the list):

https://gist.github.com/100MB Requires member (Free)

https://pastebin.com/: 512KB as guest, 10MB as Pro ($$$)

https://hastebin.com/: 400KB

Do NOT use sites like Mediafire, Dropbox, OneDrive, Google Drive, or a site that has a countdown before offering downloads.


What to provide:

...for Crashes and Runtime issues:

Minecraft 1.14.4 and newer:

Post debug.log

Older versions:

Please update...


...for Installer Issues:

Post your installer log, found in the same place you ran the installer

This log will be called either installer.log or named the same as the installer but with .log on the end

Note for Windows users:

Windows hides file extensions by default so the installer may appear without the .jar extension then when the .log is added the log will appear with the .jar extension


Where to get it:

Mojang Launcher: When using the Mojang launcher debug.log is found in .minecraft\logs.


Curse/Overwolf: If you are using the Curse Launcher, their configurations break Forge's log settings, fortunately there is an easier workaround than I originally thought, this works even with Curse's installation of the Minecraft launcher as long as it is not launched THROUGH Twitch:

  1. Make sure you have the correct version of Forge installed (some packs are heavily dependent on one specific build of Forge)
  2. Make a launcher profile targeting this version of Forge.
  3. Set the launcher profile's GameDir property to the pack's instance folder (not the instances folder, the folder that has the pack's name on it).
  4. Now launch the pack through that profile and follow the "Mojang Launcher" instructions above.






or alternately, 


Fallback ("No logs are generated"):

If you don't see logs generated in the usual place, provide the launcher_log.txt from .minecraft


Server Not Starting:


If your server does not start or a command window appears and immediately goes away, run the jar manually and provide the output.


Reporting Illegal/Inappropriate Adfocus Ads:


Get a screenshot of the URL bar or copy/paste the whole URL into a thread on the General Discussion board with a description of the Ad.

Lex will need the Ad ID contained in that URL to report it to Adfocus' support team.


Posting your mod as a GitHub Repo:


When you have an issue with your mod the most helpful thing you can do when asking for help is to provide your code to those helping you. The most convenient way to do this is via GitHub or another source control hub.

When setting up a GitHub Repo it might seem easy to just upload everything, however this method has the potential for mistakes that could lead to trouble later on, it is recommended to use a Git client or to get comfortable with the Git command line. The following instructions will use the Git Command Line and as such they assume you already have it installed and that you have created a repository.


  1. Open a command prompt (CMD, Powershell, Terminal, etc).
  2. Navigate to the folder you extracted Forge’s MDK to (the one that had all the licenses in).
  3. Run the following commands:
    1. git init
    2. git remote add origin [Your Repository's URL]
      • In the case of GitHub it should look like: https://GitHub.com/[Your Username]/[Repo Name].git
    3. git fetch
    4. git checkout --track origin/master
    5. git stage *
    6. git commit -m "[Your commit message]"
    7. git push
  4. Navigate to GitHub and you should now see most of the files.
    • note that it is intentional that some are not synced with GitHub and this is done with the (hidden) .gitignore file that Forge’s MDK has provided (hence the strictness on which folder git init is run from)
  5. Now you can share your GitHub link with those who you are asking for help.

[Workaround line, please ignore]


Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Create New...

Important Information

By using this site, you agree to our Terms of Use.