Jump to content
View in the app

A better way to browse. Learn more.
Forge Forums

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.
Please read the rules and FAQ before starting a new topic
Currently supported: All versions

Forge server using wrong java version

Frizzk
in Support & Bug Reports

Featured Replies

Posted

Hi, I have a problem with my server... I have java jdk 13 installed because I need it for netbeans. And I also have java jre 8 and jdk 8 installed too. 

The problem is that the java path is already set to jre 8, and when i use java -version on cmd, it says that I am using java 8, but when I try to open my forge server ( 1.14.4 ) it doesn't load, and in the logfile I can see that it is trying to launch with java jdk 13.

The normal minecraft server launcher starts perfectly, and my minecraft client ( with forge and mods installed ) starts without problems too (which indicates that the java version is set properly to java 8 )... I know that forge only use java 8 or java 10, but if my java version is  set to java 8, why is the forge server launcher the only one that is trying to launch with jdk 13?

 

When I uninstall jdk 13 the forge server starts perfectly, but when I install it again it doesn't. I've been searching for answer for almost three or four hours before making a post... so please, lend me a hand ??

 

Here is the latest log:

Quote

[23nov.2019 01:26:06.500] [main/INFO] [cpw.mods.modlauncher.Launcher/MODLAUNCHER]: ModLauncher running: args [--gameDir, ., --launchTarget, fmlserver, --fml.forgeVersion, 28.1.90, --fml.mcpVersion, 20190829.143755, --fml.mcVersion, 1.14.4, --fml.forgeGroup, net.minecraftforge]
[23nov.2019 01:26:06.503] [main/INFO] [cpw.mods.modlauncher.Launcher/MODLAUNCHER]: ModLauncher 4.1.0+62+5bfa59b starting: java version 13.0.1 by Oracle Corporation
[23nov.2019 01:26:06.884] [main/INFO] [net.minecraftforge.fml.loading.FixSSL/CORE]: Added Lets Encrypt root certificates as additional trust
[23nov.2019 01:26:07.391] [main/INFO] [STDERR/]: [jdk.nashorn.api.scripting.NashornScriptEngine:<init>:143]: Warning: Nashorn engine is planned to be removed from a future JDK release
[23nov.2019 01:26:07.508] [main/INFO] [STDERR/]: [jdk.nashorn.api.scripting.NashornScriptEngine:<init>:143]: Warning: Nashorn engine is planned to be removed from a future JDK release
[23nov.2019 01:26:07.511] [main/INFO] [STDERR/]: [jdk.nashorn.api.scripting.NashornScriptEngine:<init>:143]: Warning: Nashorn engine is planned to be removed from a future JDK release
[23nov.2019 01:26:07.516] [main/INFO] [STDERR/]: [jdk.nashorn.api.scripting.NashornScriptEngine:<init>:143]: Warning: Nashorn engine is planned to be removed from a future JDK release
[23nov.2019 01:26:07.521] [main/INFO] [STDERR/]: [jdk.nashorn.api.scripting.NashornScriptEngine:<init>:143]: Warning: Nashorn engine is planned to be removed from a future JDK release
[23nov.2019 01:26:07.525] [main/INFO] [STDERR/]: [jdk.nashorn.api.scripting.NashornScriptEngine:<init>:143]: Warning: Nashorn engine is planned to be removed from a future JDK release
[23nov.2019 01:26:07.527] [main/INFO] [STDERR/]: [jdk.nashorn.api.scripting.NashornScriptEngine:<init>:143]: Warning: Nashorn engine is planned to be removed from a future JDK release
[23nov.2019 01:26:07.530] [main/INFO] [STDERR/]: [jdk.nashorn.api.scripting.NashornScriptEngine:<init>:143]: Warning: Nashorn engine is planned to be removed from a future JDK release
[23nov.2019 01:26:07.533] [main/INFO] [STDERR/]: [jdk.nashorn.api.scripting.NashornScriptEngine:<init>:143]: Warning: Nashorn engine is planned to be removed from a future JDK release
[23nov.2019 01:26:07.536] [main/INFO] [STDERR/]: [jdk.nashorn.api.scripting.NashornScriptEngine:<init>:143]: Warning: Nashorn engine is planned to be removed from a future JDK release
[23nov.2019 01:26:07.539] [main/INFO] [STDERR/]: [jdk.nashorn.api.scripting.NashornScriptEngine:<init>:143]: Warning: Nashorn engine is planned to be removed from a future JDK release
[23nov.2019 01:26:07.542] [main/INFO] [STDERR/]: [jdk.nashorn.api.scripting.NashornScriptEngine:<init>:143]: Warning: Nashorn engine is planned to be removed from a future JDK release
[23nov.2019 01:26:07.548] [main/INFO] [STDERR/]: [jdk.nashorn.api.scripting.NashornScriptEngine:<init>:143]: Warning: Nashorn engine is planned to be removed from a future JDK release
[23nov.2019 01:26:07.558] [main/INFO] [STDERR/]: [jdk.nashorn.api.scripting.NashornScriptEngine:<init>:143]: Warning: Nashorn engine is planned to be removed from a future JDK release
[23nov.2019 01:26:07.564] [main/INFO] [STDERR/]: [jdk.nashorn.api.scripting.NashornScriptEngine:<init>:143]: Warning: Nashorn engine is planned to be removed from a future JDK release
[23nov.2019 01:26:07.568] [main/INFO] [STDERR/]: [jdk.nashorn.api.scripting.NashornScriptEngine:<init>:143]: Warning: Nashorn engine is planned to be removed from a future JDK release
[23nov.2019 01:26:07.575] [main/INFO] [STDERR/]: [jdk.nashorn.api.scripting.NashornScriptEngine:<init>:143]: Warning: Nashorn engine is planned to be removed from a future JDK release
[23nov.2019 01:26:07.579] [main/INFO] [STDERR/]: [jdk.nashorn.api.scripting.NashornScriptEngine:<init>:143]: Warning: Nashorn engine is planned to be removed from a future JDK release
[23nov.2019 01:26:07.587] [main/INFO] [STDERR/]: [jdk.nashorn.api.scripting.NashornScriptEngine:<init>:143]: Warning: Nashorn engine is planned to be removed from a future JDK release
[23nov.2019 01:26:07.595] [main/INFO] [STDERR/]: [jdk.nashorn.api.scripting.NashornScriptEngine:<init>:143]: Warning: Nashorn engine is planned to be removed from a future JDK release
[23nov.2019 01:26:07.612] [main/INFO] [STDERR/]: [jdk.nashorn.api.scripting.NashornScriptEngine:<init>:143]: Warning: Nashorn engine is planned to be removed from a future JDK release
[23nov.2019 01:26:07.634] [main/INFO] [STDERR/]: [jdk.nashorn.api.scripting.NashornScriptEngine:<init>:143]: Warning: Nashorn engine is planned to be removed from a future JDK release
[23nov.2019 01:26:07.639] [main/INFO] [STDERR/]: [jdk.nashorn.api.scripting.NashornScriptEngine:<init>:143]: Warning: Nashorn engine is planned to be removed from a future JDK release
[23nov.2019 01:26:07.645] [main/INFO] [STDERR/]: [jdk.nashorn.api.scripting.NashornScriptEngine:<init>:143]: Warning: Nashorn engine is planned to be removed from a future JDK release
[23nov.2019 01:26:07.649] [main/INFO] [STDERR/]: [jdk.nashorn.api.scripting.NashornScriptEngine:<init>:143]: Warning: Nashorn engine is planned to be removed from a future JDK release
[23nov.2019 01:26:07.656] [main/INFO] [STDERR/]: [jdk.nashorn.api.scripting.NashornScriptEngine:<init>:143]: Warning: Nashorn engine is planned to be removed from a future JDK release
[23nov.2019 01:26:07.665] [main/INFO] [STDERR/]: [jdk.nashorn.api.scripting.NashornScriptEngine:<init>:143]: Warning: Nashorn engine is planned to be removed from a future JDK release
[23nov.2019 01:26:07.667] [main/INFO] [STDERR/]: [jdk.nashorn.api.scripting.NashornScriptEngine:<init>:143]: Warning: Nashorn engine is planned to be removed from a future JDK release
[23nov.2019 01:26:08.881] [main/INFO] [cpw.mods.modlauncher.LaunchServiceHandler/MODLAUNCHER]: Launching target 'fmlserver' with arguments [--gameDir, .]
[23nov.2019 01:26:08.921] [main/INFO] [STDERR/]: [java.lang.ThreadGroup:uncaughtException:1049]: java.lang.RuntimeException: java.lang.IllegalArgumentException: Unsupported class file major version 57
[23nov.2019 01:26:08.921] [main/INFO] [STDERR/]: [java.lang.ThreadGroup:uncaughtException:1049]:     at cpw.mods.modlauncher.LaunchServiceHandlerDecorator.launch(LaunchServiceHandlerDecorator.java:39)
[23nov.2019 01:26:08.921] [main/INFO] [STDERR/]: [java.lang.ThreadGroup:uncaughtException:1049]:     at cpw.mods.modlauncher.LaunchServiceHandler.launch(LaunchServiceHandler.java:54)
[23nov.2019 01:26:08.922] [main/INFO] [STDERR/]: [java.lang.ThreadGroup:uncaughtException:1049]:     at cpw.mods.modlauncher.LaunchServiceHandler.launch(LaunchServiceHandler.java:72)
[23nov.2019 01:26:08.922] [main/INFO] [STDERR/]: [java.lang.ThreadGroup:uncaughtException:1049]:     at cpw.mods.modlauncher.Launcher.run(Launcher.java:81)
[23nov.2019 01:26:08.922] [main/INFO] [STDERR/]: [java.lang.ThreadGroup:uncaughtException:1049]:     at cpw.mods.modlauncher.Launcher.main(Launcher.java:65)
[23nov.2019 01:26:08.922] [main/INFO] [STDERR/]: [java.lang.ThreadGroup:uncaughtException:1049]:     at net.minecraftforge.server.ServerMain$Runner.runLauncher(ServerMain.java:63)
[23nov.2019 01:26:08.922] [main/INFO] [STDERR/]: [java.lang.ThreadGroup:uncaughtException:1049]:     at net.minecraftforge.server.ServerMain$Runner.access$100(ServerMain.java:60)
[23nov.2019 01:26:08.923] [main/INFO] [STDERR/]: [java.lang.ThreadGroup:uncaughtException:1049]:     at net.minecraftforge.server.ServerMain.main(ServerMain.java:57)
[23nov.2019 01:26:08.923] [main/INFO] [STDERR/]: [java.lang.ThreadGroup:uncaughtException:1058]: Caused by: java.lang.IllegalArgumentException: Unsupported class file major version 57
[23nov.2019 01:26:08.923] [main/INFO] [STDERR/]: [java.lang.ThreadGroup:uncaughtException:1058]:     at org.objectweb.asm.ClassReader.<init>(ClassReader.java:176)
[23nov.2019 01:26:08.923] [main/INFO] [STDERR/]: [java.lang.ThreadGroup:uncaughtException:1058]:     at org.objectweb.asm.ClassReader.<init>(ClassReader.java:158)
[23nov.2019 01:26:08.923] [main/INFO] [STDERR/]: [java.lang.ThreadGroup:uncaughtException:1058]:     at org.objectweb.asm.ClassReader.<init>(ClassReader.java:146)
[23nov.2019 01:26:08.924] [main/INFO] [STDERR/]: [java.lang.ThreadGroup:uncaughtException:1058]:     at org.objectweb.asm.ClassReader.<init>(ClassReader.java:273)
[23nov.2019 01:26:08.924] [main/INFO] [STDERR/]: [java.lang.ThreadGroup:uncaughtException:1058]:     at cpw.mods.modlauncher.TransformerClassWriter.computeHierarchy(TransformerClassWriter.java:82)
[23nov.2019 01:26:08.924] [main/INFO] [STDERR/]: [java.lang.ThreadGroup:uncaughtException:1058]:     at cpw.mods.modlauncher.TransformerClassWriter.access$100(TransformerClassWriter.java:35)
[23nov.2019 01:26:08.924] [main/INFO] [STDERR/]: [java.lang.ThreadGroup:uncaughtException:1058]:     at cpw.mods.modlauncher.TransformerClassWriter$SuperCollectingVisitor.visit(TransformerClassWriter.java:129)
[23nov.2019 01:26:08.924] [main/INFO] [STDERR/]: [java.lang.ThreadGroup:uncaughtException:1058]:     at org.objectweb.asm.ClassReader.accept(ClassReader.java:525)
[23nov.2019 01:26:08.925] [main/INFO] [STDERR/]: [java.lang.ThreadGroup:uncaughtException:1058]:     at org.objectweb.asm.ClassReader.accept(ClassReader.java:391)
[23nov.2019 01:26:08.925] [main/INFO] [STDERR/]: [java.lang.ThreadGroup:uncaughtException:1058]:     at cpw.mods.modlauncher.TransformerClassWriter.computeHierarchy(TransformerClassWriter.java:83)
[23nov.2019 01:26:08.925] [main/INFO] [STDERR/]: [java.lang.ThreadGroup:uncaughtException:1058]:     at cpw.mods.modlauncher.TransformerClassWriter.access$100(TransformerClassWriter.java:35)
[23nov.2019 01:26:08.925] [main/INFO] [STDERR/]: [java.lang.ThreadGroup:uncaughtException:1058]:     at cpw.mods.modlauncher.TransformerClassWriter$SuperCollectingVisitor.visit(TransformerClassWriter.java:129)
[23nov.2019 01:26:08.925] [main/INFO] [STDERR/]: [java.lang.ThreadGroup:uncaughtException:1058]:     at org.objectweb.asm.ClassReader.accept(ClassReader.java:525)
[23nov.2019 01:26:08.925] [main/INFO] [STDERR/]: [java.lang.ThreadGroup:uncaughtException:1058]:     at org.objectweb.asm.ClassReader.accept(ClassReader.java:391)
[23nov.2019 01:26:08.926] [main/INFO] [STDERR/]: [java.lang.ThreadGroup:uncaughtException:1058]:     at cpw.mods.modlauncher.TransformerClassWriter.computeHierarchy(TransformerClassWriter.java:83)
[23nov.2019 01:26:08.926] [main/INFO] [STDERR/]: [java.lang.ThreadGroup:uncaughtException:1058]:     at cpw.mods.modlauncher.TransformerClassWriter.access$100(TransformerClassWriter.java:35)
[23nov.2019 01:26:08.926] [main/INFO] [STDERR/]: [java.lang.ThreadGroup:uncaughtException:1058]:     at cpw.mods.modlauncher.TransformerClassWriter$SuperCollectingVisitor.visit(TransformerClassWriter.java:129)
[23nov.2019 01:26:08.926] [main/INFO] [STDERR/]: [java.lang.ThreadGroup:uncaughtException:1058]:     at org.objectweb.asm.tree.ClassNode.accept(ClassNode.java:368)
[23nov.2019 01:26:08.926] [main/INFO] [STDERR/]: [java.lang.ThreadGroup:uncaughtException:1058]:     at cpw.mods.modlauncher.TransformerClassWriter.computeHierarchy(TransformerClassWriter.java:74)
[23nov.2019 01:26:08.926] [main/INFO] [STDERR/]: [java.lang.ThreadGroup:uncaughtException:1058]:     at cpw.mods.modlauncher.TransformerClassWriter.<init>(TransformerClassWriter.java:48)
[23nov.2019 01:26:08.927] [main/INFO] [STDERR/]: [java.lang.ThreadGroup:uncaughtException:1058]:     at cpw.mods.modlauncher.ClassTransformer.transform(ClassTransformer.java:120)
[23nov.2019 01:26:08.927] [main/INFO] [STDERR/]: [java.lang.ThreadGroup:uncaughtException:1058]:     at cpw.mods.modlauncher.TransformingClassLoader$DelegatedClassLoader.findClass(TransformingClassLoader.java:241)
[23nov.2019 01:26:08.927] [main/INFO] [STDERR/]: [java.lang.ThreadGroup:uncaughtException:1058]:     at cpw.mods.modlauncher.TransformingClassLoader.loadClass(TransformingClassLoader.java:128)
[23nov.2019 01:26:08.927] [main/INFO] [STDERR/]: [java.lang.ThreadGroup:uncaughtException:1058]:     at cpw.mods.modlauncher.TransformingClassLoader.loadClass(TransformingClassLoader.java:98)
[23nov.2019 01:26:08.927] [main/INFO] [STDERR/]: [java.lang.ThreadGroup:uncaughtException:1058]:     at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521)
[23nov.2019 01:26:08.928] [main/INFO] [STDERR/]: [java.lang.ThreadGroup:uncaughtException:1058]:     at java.base/java.lang.Class.forName0(Native Method)
[23nov.2019 01:26:08.928] [main/INFO] [STDERR/]: [java.lang.ThreadGroup:uncaughtException:1058]:     at java.base/java.lang.Class.forName(Class.java:416)
[23nov.2019 01:26:08.928] [main/INFO] [STDERR/]: [java.lang.ThreadGroup:uncaughtException:1058]:     at net.minecraftforge.fml.loading.FMLServerLaunchProvider.lambda$launchService$0(FMLServerLaunchProvider.java:51)
[23nov.2019 01:26:08.928] [main/INFO] [STDERR/]: [java.lang.ThreadGroup:uncaughtException:1058]:     at cpw.mods.modlauncher.LaunchServiceHandlerDecorator.launch(LaunchServiceHandlerDecorator.java:37)
[23nov.2019 01:26:08.928] [main/INFO] [STDERR/]: [java.lang.ThreadGroup:uncaughtException:1058]:     ... 7 more
 

 

Edited by Frizzk

Instead of invoking "java", use the full path to the Java 8 java.exe

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
  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.

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.

 

  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]

 

  • Author

Hey thanks for replying, but I did not understand you... what do you mean with "invoking"? When i'm going to start the server I just double click the "forge-1.14.4-28.1.90.jar" and nothing happens, it only creates the log file. Could you be a bit more explicative? I don't know if there is a way to start it with a .bat file if thats what you say.

  • Author

Thank you so much!! I'll leave here what I did to get it working just for helping other users that have the same issues:

 

- I opened a cmd console in the server folder ( shift + right click, and then open powershell ).

- I wrote "java -jar forge.jar" and then it started with java 1.8.

 

When I put the full path to the java executable it says "C:\Program is not a valid command", so I tried to use just  "java" and it worked. Thank you again for the help!!

  • 1 year later...
On 11/23/2019 at 8:57 AM, diesieben07 said:

You can run a jar file from the command line using java -jar jar file here. If you use the full path to the java executable instead of just java you can specify which Java to use.

Full path? I have been having this issue and as the other person stated, it simply says it is not a valid command. 

Do you have an example of the code required?

  • 2 weeks later...
On 8/5/2021 at 8:03 AM, ThreeForths said:

Full path? I have been having this issue and as the other person stated, it simply says it is not a valid command. 

Do you have an example of the code required?

It's very weird. This is how I did it, running this from the server folder

"C:\Program Files\Java\jre1.8.0_301\bin\java.exe" -Xmx8096M -Xms2096M -jar forge-1.12.2-14.23.5.2854.jar

  • 9 months later...
On 8/12/2021 at 6:48 PM, EpicGamerViscus said:

It's very weird. This is how I did it, running this from the server folder

"C:\Program Files\Java\jre1.8.0_301\bin\java.exe" -Xmx8096M -Xms2096M -jar forge-1.12.2-14.23.5.2854.jar

I'm having a similar problem but that method doesn't seem to work for me. I think the quotes might be messing it up but I am unsure on that. If I remove the quotes it can't detect the space between program and files at the beginning as one filename, so it assumes you are trying to run a command called C:\Program, which doesn't exist, and not trying to follow a set file path. I am trying to find a way to bypass this by using file shortcuts but it isn't working. It keeps saying that they cannot find that file path.

I used this
"C:\Program Files\Java\jre1.8.0_333\bin\jave.exe" -Xmx16G -Xms8G -jar "Blightfall.jar" nogui
Which didn't work, and when I use this
C:\Program Files\Java\jre1.8.0_333\bin\jave.exe -Xmx16G -Xms8G -jar "Blightfall.jar" nogui
It recognizes C:\Program as a separate thing to the rest

  • Guest locked this topic
Guest
This topic is now closed to further replies.
https://forums.minecraftforge.net/topic/78181-forge-server-using-wrong-java-version/
Go to topic listing

Important Information

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

I accept

Configure browser push notifications
Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.