Kayduxer Posted February 27, 2020 Share Posted February 27, 2020 Hi again! I have updated my Forge server to version 1.15.2 (build 31.1.17), but players are unable to access the server. Client logs: launcher_log.txt latest.log debug.log Server logs: latest.log debug.log Quote Link to comment Share on other sites More sharing options...
DaemonUmbra Posted February 27, 2020 Share Posted February 27, 2020 I can’t see anything wrong here but I’m on mobile. When you say they can’t access it what do you mean? Quote 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. Spoiler Logs (Most issues require logs to diagnose): Spoiler 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: Spoiler Make sure you have the correct version of Forge installed (some packs are heavily dependent on one specific build of Forge) Make a launcher profile targeting this version of Forge. 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). Now launch the pack through that profile and follow the "Mojang Launcher" instructions above. Video: Spoiler 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: Spoiler 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: Spoiler 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: Spoiler 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. Open a command prompt (CMD, Powershell, Terminal, etc). Navigate to the folder you extracted Forge’s MDK to (the one that had all the licenses in). Run the following commands: git init 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 git fetch git checkout --track origin/master git stage * git commit -m "[Your commit message]" git push 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) 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 More sharing options...
Kayduxer Posted February 27, 2020 Author Share Posted February 27, 2020 Ok, I solved the problem. Wait me please, I want to explain later how to avoid this type of issues. Quote Link to comment Share on other sites More sharing options...
Kayduxer Posted February 28, 2020 Author Share Posted February 28, 2020 Ok, here are some tips to avoid problems with running Forge servers. This currently applies for version 1.15.2, build 31.1.17. I strongly recommend that the connection be direct, that is, without a proxy in between. To date, BungeeCord does not offer support for Forge, so it is better not to waste time trying. If you decide to use VelocityProxy (which does offer support for Forge servers), I recommend using the modern player info forwading. Why? Because if you use "legacy" or, failing that, none, you will get immediate disconnection errors due to the inability to find a valid uuid. You may also get errors such as that you must install the Forge client when you already have it, or that you need certain mods when you actually have them all. Currently it is not possible to connect through VelocityProxy with the modern system, since «Fabric» (with which it is possible to link the Forge server with the proxy) does not offer support for the latest build, and it is for this reason that I advise to use a Direct connection to the Forge server. I remind CentOS 7 users (server side) that they must configure the iptables and the firewall correctly, to avoid errors of the type "java.net.NoRouteToHostException: No route to host", among others. When it comes to installing mods, I recommend installing them all one by one. In case one has an error, they will know what it is. Something important to remember is that, if you are going to install the mods one by one, you must delete the “world” folder before including a new mod. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
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.