Related ports: 443 5916 8000 9999 10001 12001 881 8081
« back to SG Ports
External Resources SANS Internet Storm Center: port 8082
Notes: Port numbers in computer networking represent communication endpoints. Ports are unsigned 16-bit integers (0-65535) that identify a specific process, or network service. IANA is responsible for internet protocol resources, including the registration of commonly used port numbers for well-known internet services. Well Known Ports: 0 through 1023. Registered Ports: 1024 through 49151. Dynamic/Private : 49152 through 65535. TCP ports use the Transmission Control Protocol, the most commonly used protocol on the Internet and any TCP/IP network. TCP enables two hosts to establish a connection and exchange streams of data. TCP guarantees delivery of data and that packets will be delivered in the same order in which they were sent. Guaranteed communication/delivery is the key difference between TCP and UDP. UDP ports use the Datagram Protocol. Like TCP, UDP is used in combination with IP (the Internet Protocol) and facilitates the transmission of datagrams from one computer to applications on another computer, but unlike TCP, UDP is connectionless and does not guarantee reliable communication; it's up to the application that received the message to process any errors and verify correct delivery. UDP is often used with time-sensitive applications, such as audio/video streaming and realtime gaming, where dropping some packets is preferable to waiting for delayed data. When troubleshooting unknown open ports, it is useful to find exactly what services/processes are listening to them. This can be accomplished in both Windows command prompt and Linux variants using the "netstat -aon" command. We also recommend runnig multiple anti-virus/anti-malware scans to rule out the possibility of active malicious software. For more detailed and personalized help please use our forums.
- SG Ports Database » Vulnerable Ports
- SG Security Scan » Scanned Ports » Commonly Open Ports
- SG Broadband Tools
- All Known Ports
- All Vulnerable Ports
- Scanned Ports
- Recently Updated Ports
- Popular Ports/Ranges
- SG Security Scan
Understanding Default Open Ports
By default, Aruba controllers and access points treat ports as untrusted. However, certain ports are open by default only on the trusted side of the network. These open ports are listed in Table 1 .
- Stack Overflow Public questions & answers
- Stack Overflow for Teams Where developers & technologists share private knowledge with coworkers
- Talent Build your employer brand
- Advertising Reach developers & technologists worldwide
- About the company
Collectives™ on Stack Overflow
Find centralized, trusted content and collaborate around the technologies you use most.
Q&A for work
Connect and share knowledge within a single location that is structured and easy to search.
Cannot connect to localhost:8082
After successful running the maven project in eclipse, I cannot connect to http://localhost:8082 . It shows the below error:
connection refused
What should I do to resolve the problem?
2 Answers 2
This exception usually occurs when there is no service listening on the port you are trying to connect to. A couple of things could be happening:
- You have not started your server.
- Your server is not waiting to accept connections.
- You are trying to connect to the wrong port number.
You should check your services. I think they are either stopped or not working. You can check the services:- a) if using windows by clicking services in control panel b) if using linux type in the command Line sudo mqsql service. you can refer this link- https://www.cyberciti.biz/faq/how-to-find-out-if-mysql-is-running-on-linux/
2)Also check the database connection string might you have not used correct string.
Your Answer
Sign up or log in, post as a guest.
Required, but never shown
By clicking “Post Your Answer”, you agree to our terms of service , privacy policy and cookie policy
Not the answer you're looking for? Browse other questions tagged maven localhost or ask your own question .
- The Overflow Blog
- How Intuit democratizes AI development across teams through reusability sponsored post
- The nature of simulating nature: A Q&A with IBM Quantum researcher Dr. Jamie...
- Featured on Meta
- We've added a "Necessary cookies only" option to the cookie consent popup
- The [amazon] tag is being burninated
- Launching the CI/CD and R Collectives and community editing features for...
- Staging Ground Beta 1 Recap, and Reviewers needed for Beta 2
- Temporary policy: ChatGPT is banned
Hot Network Questions
- will thumb also get callus on strumming guitar
- Largest Binary Area
- Why are physically impossible and logically impossible concepts considered separate in terms of probability?
- Why are non-Western countries siding with China in the UN?
- Confusion About Entropy
- Book about a good dark lord, think "not Sauron"
- How to prove that the supernatural or paranormal doesn't exist?
- Can I tell police to wait and call a lawyer when served with a search warrant?
- How do you get out of a corner when plotting yourself into a corner
- The number of distinct words in a sentence
- Resistance against timing attacks of AES candidates
- What is the number of bands in GPAW?
- How to handle missing value if imputation doesnt make sense
- Nought and Crosses (tic-tac-toe) in C++
- Acidity of alcohols and basicity of amines
- Wahoo Kickr with 8 speed cassette?
- Experiment to crush soda can by air pressure
- Is a PhD visitor considered as a visiting scholar?
- Why is there a voltage on my HDMI and coaxial cables?
- 2000s era show about a group of friends who used a remote to open a portal anytime they needed to escape from aliens or creatures
- Is there a proper earth ground point in this switch box?
- FAA Handbooks Copyrights
- Is lock-free synchronization always superior to synchronization using locks?
- If you order a special airline meal (e.g. vegan) just to try it, does this inconvenience the caterers and staff?
Your privacy
By clicking “Accept all cookies”, you agree Stack Exchange can store cookies on your device and disclose information in accordance with our Cookie Policy .
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Ports used in Configuration Manager
- 20 minutes to read
- 8 contributors
Applies to: Configuration Manager (current branch)
This article lists the network ports that Configuration Manager uses. Some connections use ports that aren't configurable, and some support custom ports that you specify. If you use any port filtering technology, verify that the required ports are available. These port filtering technologies include firewalls, routers, proxy servers, or IPsec.
If you support internet-based clients by using SSL bridging, in addition to port requirements, you might also have to allow some HTTP verbs and headers to traverse your firewall.
Ports you can configure
Configuration Manager enables you to configure the ports for the following types of communication:
Enrollment proxy point to enrollment point
Client-to-site systems that run IIS
Client to internet (as proxy server settings)
Software update point to internet (as proxy server settings)
Software update point to WSUS server
Site server to site database server
Site server to WSUS database server
Reporting services points
You configure the ports for the reporting services point in SQL Server Reporting Services. Configuration Manager then uses these ports during communications to the reporting services point. Be sure to review these ports that define the IP filter information for IPsec policies or for configuring firewalls.
By default, the HTTP port that's used for client-to-site system communication is port 80, and 443 for HTTPS. You can change these ports during setup or in the site properties.
Non-configurable ports
Configuration Manager doesn't allow you to configure ports for the following types of communication:
Site to site
Site server to site system
Configuration Manager console to SMS Provider
Configuration Manager console to the internet
Connections to cloud services, such as Microsoft Azure
Ports used by clients and site systems
The following sections detail the ports that are used for communication in Configuration Manager. The arrows in the section title show the direction of the communication:
--> Indicates that one computer starts communication and the other computer always responds
<--> Indicates that either computer can start communication
Asset Intelligence synchronization point --> Microsoft
Asset Intelligence synchronization point --> SQL Server
Client --> client.
Wake-up proxy also uses ICMP echo request messages from one client to another client. Clients use this communication to confirm whether the other client is awake on the network. ICMP is sometimes referred to as ping commands. ICMP doesn't have a UDP or TCP protocol number, and so it isn't listed in the below table. However, any host-based firewalls on these client computers or intervening network devices within the subnet must permit ICMP traffic for wake-up proxy communication to succeed.
For more information, see Windows PE Peer Cache .
Client --> Configuration Manager Network Device Enrollment Service (NDES) policy module
Client --> cloud distribution point.
For more information, see Ports and data flow .
Client --> Cloud management gateway (CMG)
For more information, see CMG data flow .
Client --> Distribution point, both standard and pull
Use client settings to configure the alternate port for express updates. For more information, see Port that clients use to receive requests for delta content .
Client --> Distribution point configured for multicast, both standard and pull
Client --> distribution point configured for pxe, both standard and pull.
If you enable a host-based firewall, make sure that the rules allow the server to send and receive on these ports. When you enable a distribution point for PXE, Configuration Manager can enable the inbound (receive) rules on the Windows Firewall. It doesn't configure the outbound (send) rules.
Client --> Fallback status point
Client --> Global catalog domain controller
A Configuration Manager client doesn't contact a global catalog server when it's a workgroup computer or when it's configured for internet-only communication.
Client --> Management point
Client --> software update point, client --> state migration point, cmg connection point --> cmg virtual machine scale set.
Configuration Manager uses these connections to build the CMG channel. For more information, see CMG data flow .
CMG connection point --> CMG classic cloud service
Cmg connection point --> management point.
The specific port required depends upon the management point configuration. For more information, see CMG data flow .
CMG connection point --> Software update point
The specific port depends upon the software update point configuration.
Configuration Manager console --> Client
Configuration Manager console --> internet
The Configuration Manager console uses internet access for the following actions:
- Downloading software updates from Microsoft Update for deployment packages.
- The Feedback item in the ribbon.
- Links to documentation within the console.
- Downloading items from Community hub
Configuration Manager console --> Reporting services point
Configuration manager console --> site server, configuration manager console --> sms provider, note for administration service.
Any device that makes a call to the administration service on the SMS Provider uses HTTPS port 443. For more information, see What is the administration service?
Configuration Manager Network Device Enrollment Service (NDES) policy module --> Certificate registration point
Data warehouse service point --> sql server, distribution point, both standard and pull --> management point.
A distribution point communicates to the management point in the following scenarios:
To report the status of prestaged content
To report usage summary data
To report content validation
To report the status of package downloads, only for pull-distribution points
Endpoint Protection point --> internet
Endpoint Protection point --> SQL Server
Enrollment proxy point --> enrollment point, enrollment point --> sql server, exchange server connector --> exchange online, exchange server connector --> on-premises exchange server, mac computer --> enrollment proxy point.
Management point --> Domain controller
Management point <--> Site server
Management point --> sql server, mobile device --> enrollment proxy point, pull-distribution point --> distribution point configured as source, reporting services point --> sql server, service connection point --> azure (cmg).
Service connection point --> Azure Logic App
For more information, see External notifications .
Site server <--> Asset Intelligence synchronization point
Site server --> client, site server --> cloud distribution point, site server --> distribution point, both standard and pull.
Site server --> Domain controller
Site server <--> Certificate registration point
Site server <--> cmg connection point, site server <--> endpoint protection point, site server <--> enrollment point, site server <--> enrollment proxy point, site server <--> fallback status point, site server --> internet, site server <--> issuing certification authority (ca).
This communication is used when you deploy certificate profiles by using the certificate registration point. The communication isn't used for every site server in the hierarchy. Instead, it's used only for the site server at the top of the hierarchy.
Site server --> Server hosting remote content library share
You can move the content library to another storage location to free up hard drive space on your central administration or primary site servers. For more information, see Configure a remote content library for the site server .
Site server <--> Service connection point
Site server <--> reporting services point, site server <--> site server, site server --> sql server.
During the installation of a site that uses a remote SQL Server to host the site database, open the following ports between the site server and the SQL Server:
Site server --> SQL Server for WSUS
Site server --> sms provider, site server <--> software update point, site server <--> state migration point, sms provider --> sql server.
Software update point --> internet
Software update point --> Upstream WSUS server
SQL Server --> SQL Server
Intersite database replication requires the SQL Server at one site to communicate directly with the SQL Server at its parent or child site.
Configuration Manager doesn't require the SQL Server Browser, which uses port UDP 1434.
State migration point --> SQL Server
Notes for ports used by clients and site systems, note 1: proxy server port.
This port can't be configured but can be routed through a configured proxy server.
Note 2: Alternate port available
You can define an alternate port in Configuration Manager for this value. If you define a custom port, use that custom port in the IP filter information for IPsec policies or to configure firewalls.
Note 3: Windows Server Update Services (WSUS)
Since Windows Server 2012, by default WSUS uses port 8530 for HTTP and port 8531 for HTTPS.
After installation, you can change the port. You don't have to use the same port number throughout the site hierarchy.
If the HTTP port is 80, the HTTPS port must be 443.
If the HTTP port is anything else, the HTTPS port must be 1 or higher, for example, 8530 and 8531.
When you configure the software update point to use HTTPS, the HTTP port must also be open. Unencrypted data, such as the EULA for specific updates, uses the HTTP port.
The site server makes a connection to the SQL Server hosting the SUSDB when you enable the following options for WSUS cleanup:
- Add non-clustered indexes to the WSUS database to improve WSUS cleanup performance
- Remove obsolete updates from the WSUS database
If you change the default SQL Server port to an alternate port with SQL Server Configuration Manager, make sure the site server can connect using the defined port. Configuration Manager doesn't support dynamic ports. By default, SQL Server named instances use dynamic ports for connections to the database engine. When you use a named instance, manually configure the static port.
Note 4: Trivial FTP (TFTP) Daemon
The Trivial FTP (TFTP) Daemon system service doesn't require a user name or password and is an integral part of Windows Deployment Services (WDS). The Trivial FTP Daemon service implements support for the TFTP protocol that's defined by the following RFCs:
RFC 1350: TFTP
RFC 2347: Option extension
RFC 2348: Block size option
RFC 2349: Time-out interval and transfer size options
TFTP is designed to support diskless boot environments. TFTP Daemons listen on UDP port 69 but respond from a dynamically allocated high port. If you enable this port, the TFTP service can receive incoming TFTP requests, but the selected server can't respond to those requests. You can't enable the selected server to respond to inbound TFTP requests unless you configure the TFTP server to respond from port 69.
The PXE-enabled distribution point and the client in Windows PE select dynamically allocated high ports for TFTP transfers. These ports are defined by Microsoft between 49152 and 65535. For more information, see Service overview and network port requirements for Windows .
However, during the actual PXE boot, the network card on the device selects the dynamically allocated high port it uses during the TFTP transfer. The network card on the device isn't bound to the dynamically allocated high ports defined by Microsoft. It's only bound to the ports defined in RFC 1350. This port can be any from 0 to 65535. For more information about what dynamically allocated high ports the network card uses, contact the device hardware manufacturer.
Note 5: Communication between the site server and site systems
By default, communication between the site server and site systems is bi-directional. The site server starts communication to configure the site system, and then most site systems connect back to the site server to send status information. Reporting service points and distribution points don't send status information. If you select Require the site server to initiate connections to this site system on the site system properties after the site system has been installed, the site system won't start communication with the site server. Instead, the site server starts the communication. It uses the site system installation account for authentication to the site system server.
Note 6: Dynamic ports
Dynamic ports use a range of port numbers that's defined by the OS version. These ports are also known as ephemeral ports. For more information about the default port ranges, see Service overview and network port requirements for Windows .
Other ports
The following sections provide more information about ports that Configuration Manager uses.
Client to server shares
Clients use Server Message Block (SMB) whenever they connect to UNC shares. For example:
Manual client installation that specifies the CCMSetup.exe /source: command-line property
Endpoint Protection clients that download definition files from a UNC path
Connections to SQL Server
For communication to the SQL Server database engine and for intersite replication, you can use the default SQL Server port or specify custom ports:
Intersite communications use:
SQL Server Service Broker, which defaults to port TCP 4022.
SQL Server service, which defaults to port TCP 1433.
Intrasite communication between the SQL Server database engine and various Configuration Manager site system roles defaults to port TCP 1433.
Configuration Manager uses the same ports and protocols to communicate with each SQL Server Always On availability group replica that hosts the site database as if the replica was a standalone SQL Server instance.
When you use Azure and the site database is behind an internal or external load balancer, configure the following components:
- Firewall exceptions on each replica
- Load-balancing rules
Configure the following ports:
- SQL over TCP: TCP 1433
- SQL Server Service Broker: TCP 4022
- Server Message Block (SMB): TCP 445
- RPC Endpoint Mapper: TCP 135
Configuration Manager doesn't support dynamic ports. By default, SQL Server named instances use dynamic ports for connections to the database engine. When you use a named instance, manually configure the static port for intrasite communication.
The following site system roles communicate directly with the SQL Server database:
Certificate registration point role
Enrollment point role
Management point
Site server
Reporting Services point
SMS Provider
When a SQL Server hosts a database from more than one site, each database must use a separate instance of SQL Server. Configure each instance with a unique set of ports.
If you enable a host-based firewall on the SQL Server, configure it to allow the correct ports. Also configure network firewalls in between computers that communicate with the SQL Server.
For an example of how to configure SQL Server to use a specific port, see Configure a server to listen on a specific TCP port .
Discovery and publishing
Configuration Manager uses the following ports for the discovery and publishing of site information:
- Lightweight Directory Access Protocol (LDAP): 389
- Secure LDAP (LDAPS, for signing and binding): 636
- Global catalog LDAP: 3268
- RPC Endpoint Mapper: 135
- RPC: Dynamically allocated high TCP ports
- TCP: 1024: 5000
- TCP: 49152: 65535
External connections made by Configuration Manager
On-premises Configuration Manager clients or site systems can make the following external connections:
Site server <--> Issuing Certification Authority (CA)
Software update point --> Upstream WSUS Server
Service connection point --> Azure
CMG connection point --> CMG cloud service
Installation requirements for site systems that support internet-based clients
This section only applies to internet-based client management (IBCM). It doesn't apply to the cloud management gateway. For more information, see Manage clients on the internet .
Internet-based management points, distribution points that support internet-based clients, the software update point, and the fallback status point use the following ports for installation and repair:
Site server --> Site system: RPC endpoint mapper using UDP and TCP port 135
Site server --> Site system: RPC dynamic TCP ports
Site server <--> Site system: Server message blocks (SMB) using TCP port 445
Application and package installations on distribution points require the following RPC ports:
Site server --> Distribution point: RPC endpoint mapper using UDP and TCP port 135
Site server --> Distribution point: RPC dynamic TCP ports
Use IPsec to help secure the traffic between the site server and site systems. If you must restrict the dynamic ports that are used with RPC, you can use the Microsoft RPC configuration tool (rpccfg.exe). Use the tool to configure a limited range of ports for these RPC packets. For more information, see How to configure RPC to use certain ports and how to help secure those ports by using IPsec .
Before you install these site systems, make sure that the remote registry service is running on the site system server and that you have specified a site system installation account if the site system is in a different Active Directory forest without a trust relationship. For example, the remote registry service is used on servers running site systems such as distribution points (both pull and standard) and remote SQL Servers.
Ports used by Configuration Manager client installation
The ports that Configuration Manager uses during client installation depends on the deployment method:
For a list of ports for each client deployment method, see Ports used during Configuration Manager client deployment
For more information about how to configure Windows Firewall on the client for client installation and post-installation communication, see Windows Firewall and port settings for clients
Ports used by migration
The site server that runs migration uses several ports to connect to applicable sites in the source hierarchy. For more information, see Required configurations for migration .
Ports used by Windows Server
The following table lists some of the key ports used by Windows Server.
For more information, see the following articles:
Service overview and network port requirements for Windows
How to configure a firewall for domains and trusts
The following diagram shows the connections between the main components that are in a typical Configuration Manager site. It currently doesn't include all connections.
Proxy server support
Internet access requirements
Submit and view feedback for
Additional resources
- IPv4 Subnet Calculator
- Password Generator/Decryptor
- MAC Address Finder
TCP/UDP Port Finder
Search results for "8082".
- Service Details Source
- us-cli Utilistor (Client) IANA
- EMC2 (Legato) Networker or Sun Solcitice Backup (Official) WIKI
- blackice BlackICE ICEcap SANS
- irdmi Web service, iTunes Radio streams Apple
- QuickTime Streaming Server Apple
About TCP/UDP ports
Recent searches.
- Skip to main content
- Skip to footer
Audit My PC - Free Internet Security Audit
Firewall Test and web tools to check your security and privacy
Looking for information on Protocol TCP 8082 ? This page will attempt to provide you with as much port information as possible on TCP Port 8082.
TCP Port 8082 may use a defined protocol to communicate depending on the application. A protocol is a set of formalized rules that explains how data is communicated over a network. Think of it as the language spoken between computers to help them communicate more efficiently.
Protocol HTTP for example defines the format for communication between internet browsers and web sites. Another example is the IMAP protocol that defines the communication between IMAP email servers and clients or finally, the SSL protocol which states the format to use for encrypted communications.
TCP Port 8082
Here is what we know about protocol TCP Port 8082 . If you have information on TCP port 8082 that is not reflected on this page, simply leave a comment and we’ll update our information.
PORT 8082 – Information
- Port Number: 8082
- TCP / UDP: TCP
- Delivery: Yes
- Protocol / Name: blackice-alerts
- Port Description: BlackIce Alerts. Alerting port for BlackIce’s \Network Ice\ host-based firewall/intrusion detection program. See Security Concerns above (8081).
Side note: TCP port 8082 uses the Transmission Control Protocol. TCP is one of the main protocols in TCP/IP networks. Whereas the IP protocol deals only with packets, TCP enables two hosts to establish a connection and exchange streams of data. TCP guarantees delivery of data and also guarantees that packets will be delivered on port 8082 in the same order in which they were sent. Guaranteed communication over port 8082 is the key difference between TCP and UDP. UDP port 8082 would not have guaranteed communication in the same way as TCP.
Because protocol TCP port 8082 was flagged as a virus (colored red) does not mean that a virus is using port 8082, but that a Trojan or Virus has used this port in the past to communicate.
TCP 8082 – Disclaimer
We do our best to provide you with accurate information on PORT 8082 and work hard to keep our database up to date. This is a free service and accuracy is not guaranteed. We do our best to correct any errors and welcome feedback!
Reader Interactions
hi, i can open the por 8082 for use another program?
Leave a Reply
Your email address will not be published. Required fields are marked *
Miscellaneous
- Free Address Finder
- HTML Encoder Decoder
- Website Monitoring
- Whats My IP Address?
Service Name and Transport Protocol Port Number Registry
Contact Information
How to change Artifactory’s service port
In this KB article we will demonstrate how you can change Artifactory’s service port in both versions 6.x and 7.x
Artifactory uses port 8081 by default. In version 6.x this port is also used to access the web UI. In version 7.x the web UI is accessible via port 8082 and Artifactory’s service is still using port 8081.
In this example, we will change the port from 8081 to 8080.
Instructions for version 7.x: Navigate to $JFROG_HOME/artifactory/etc/ Edit the “ system.yaml ” file and add the following values: artifactory: port: 8080
Make sure that artifactory is not indented and that the port value is indented with 4 spaces .
Restart Artifactory for the change to take effect.
More information can be found here .
Instructions for version 6.x: Navigate to $ARTIFACTORY_HOME/tomcat/conf/ directory Edit the “ server.xml ” file to modify the port number from 8081 to 8080
In order to change Artifactory’s port number to 8080 it would be required to change the line: <Connector port=" 8081 " sendReasonPhrase="true" relaxedPathChars='[]' relaxedQueryChars='[]' maxThreads="200"/> To <Connector port=" 8080 " sendReasonPhrase="true" relaxedPathChars='[]' relaxedQueryChars='[]' maxThreads="200"/>
Restart Artifactory to apply the changes.
Release Fast Or Die
Your action was successful
Oops... Something went wrong
Please try again later
Information
Modal Message
Stack Exchange Network
Stack Exchange network consists of 181 Q&A communities including Stack Overflow , the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.
Geographic Information Systems Stack Exchange is a question and answer site for cartographers, geographers and GIS professionals. It only takes a minute to sign up.
Q&A for work
Connect and share knowledge within a single location that is structured and easy to search.
How to change GeoServer port from 8082 to 80?
How can I change the port GeoServer is running on from 8082 (in OSGeo Live VMs) to 80?
There is a related question here in GIS.SE., but the answers were about changing the underlying tomcat port from 8080 to 80 in /etc/tomcat*/server.xml .
Apparently, the above solution is based on assuming tomcat and GeoServer to run on the same port. But in OSGeoLive 10 VM, the tomcat port ( 8080 ) is different from the GeoSever port ( 8082 ). Also related is the SO answer here about how to change tomcat port to 80.
By the way, I am using OSGeoLive 10, with apache on 80 (??), tomcat8 on 8080, and GeoServer on 8082.
I am also confused about the relationship between apache, tomcat and GeoServer. Wouldn't changing the tomcat port to 80 cause conflicts with apache? Why are GeoSever running in different ports with tomcat and apache?
To clarify, I'd like to avoid using proxies and port forwarding if possible, as I remember having issues with them, e.g. here and about CORS. (It's most likely that I didn't fully understand proxy right).
Also, I need to be consistent between my GeoSever installation on 8082, and someone else's installation on port 80. The target server that I am trying to match does not seem to have a2enmod , libapache2-mod-jk installed (by checking apt-get ). It seems to be a minimal installation and its /etc/tomcat7/server.xml is as listed below.
Any pointers on how I can match the settings of the target server? What other configurations files (if any) should I look into to mimic the target?
- If someone else is using port 80 you are out of luck – Ian Turton ♦ Jan 13, 2017 at 16:39
- @iant The thing is that the target server seems to run apache and GeoSever both on 80 and it seems to be OK. If possible, this seems to be an easier solution for me than the current OSGeo configuration. – tinlyx Jan 13, 2017 at 17:32
- 1 Then someone is proxying – Ian Turton ♦ Jan 13, 2017 at 17:33
- @iant Any pointers on where the proxy settings might be? It seems that the server does not have mod_jk or a2enmod . The tomcat config is attached in the question. Is it somewhere in /etc/apach2 ? Both systems are Lubuntu 16.04 – tinlyx Jan 13, 2017 at 17:40
2 Answers 2
GeoServer is a servlet and always runs inside a servlet container (e.g. tomcat, jetty, JBoss etc). So your question is "how do I change the port of the container that GeoServer is using?" which is what the question you point to is answering.
On the OSGeoLive VM there are two tomcat containers running one on port 8080 and the other (with GeoServer) on 8082. Apache httpd is running on port 80 to server static web pages and cgi based programs like MapServer.
To access GeoServer through port 80 the usual procedure is to use mod_jk to forward requests to machine:80/geoserver to localhost:8080/geoserver . This process is off topic here but widely covered elsewhere .
- Thanks for your answer. Is there a way to avoid proxy and forwarding? I have a target server that I need to match which did not seem to have involved mod_jk . Please see my update. – tinlyx Jan 13, 2017 at 16:28
This is what worked for me on OSGeo Live after some trials.
OSGeoLive is running GeoServer on jetty. Hence the different port number 8082 than the tomcat port 8080 .
Given the packages already in OSGeo Live, I only needed to set up a proxy (as pointed out by @iant) by editing one of the apache2 configuration files, e.g. /etc/apache2/sites-enabled/000-default.conf and adding the following just before </VirtualHost> (and then restart apache2):
- Proxy * is a bit extreme. Why not just proxy /geoserver – nmtoken Jan 14, 2017 at 11:48
- @nmtoken Thanks. I've updated the answer as suggested. – tinlyx Jan 14, 2017 at 20:34
Your Answer
Sign up or log in, post as a guest.
Required, but never shown
By clicking “Post Your Answer”, you agree to our terms of service , privacy policy and cookie policy
Not the answer you're looking for? Browse other questions tagged geoserver apache tomcat or ask your own question .
- The Overflow Blog
- How Intuit democratizes AI development across teams through reusability sponsored post
- The nature of simulating nature: A Q&A with IBM Quantum researcher Dr. Jamie...
- Featured on Meta
- We've added a "Necessary cookies only" option to the cookie consent popup
Hot Network Questions
- Experiment to crush soda can by air pressure
- Do you really get double penalized for rolling HSA excess contributions to the next year?
- The number of distinct words in a sentence
- Resistance against timing attacks of AES candidates
- Is it correct to use "the" before "materials used in making buildings are"?
- How to handle missing value if imputation doesnt make sense
- Can I tell police to wait and call a lawyer when served with a search warrant?
- How many "grounds" are there and what is the difference?
- 2000s era show about a group of friends who used a remote to open a portal anytime they needed to escape from aliens or creatures
- Draw Parcly Taxel's cutie mark
- Is there a proper earth ground point in this switch box?
- Do roots of these polynomials approach the negative of the Euler-Mascheroni constant?
- Why are physically impossible and logically impossible concepts considered separate in terms of probability?
- Replacing broken pins/legs on a DIP IC package
- Stats update during Index rebuild
- Is a PhD visitor considered as a visiting scholar?
- Has 90% of ice around Antarctica disappeared in less than a decade?
- Acidity of alcohols and basicity of amines
- OK to delete Windows.db file on PC?
- FAA Handbooks Copyrights
- Did any DOS compatibility layers exist for any UNIX-like systems before DOS started to become outmoded?
- Getting timestamp of each time pings enter and leave a radius
- Transgenic Peach DNA Splicing
- What is the number of bands in GPAW?
Your privacy
By clicking “Accept all cookies”, you agree Stack Exchange can store cookies on your device and disclose information in accordance with our Cookie Policy .
Installation: SAP Mobile Platform Server for Linux
Http/https port number reference.
HTTP and HTTPS ports, default assignments, and protocols.
Disabling HTTP/HTTPS Ports
To disable HTTP or HTTPS ports after installation, you can edit the SMP_HOME /Server/config_master/org.eclipse.gemini.web.tomcat/default-server.xml file. You should be familiar with XML.
Before you begin, back up the default-server.xml file, and save it to a secure location.
noSSL – for runtime services from the SDK using the HTTP protocol.
oneWaySSL – for runtime services from the SDK using the HTTPS protocol.
mutualSSL – for runtime services from the SDK using the HTTPS protocol, with client and server certificates.
AdminSSL – for Administrative services that are used by Management Cockpit.
Edit the default-server.xml file, and delete the entire noSSL connector XML element.
Save the file, and restart the server.
Edit the default-server.xml file, and delete the oneWaySSL and the mutualSSL connectors; remove the entire XML elements.
- Redefine the AdminSSL connector XML element as: <Connector smpConnectorName="AdminSSL" protocol="HTTP/1.1" port="8083" maxThreads="200" smpServiceType="admin" compression="on" compressionMinSize="2048" compressableMimeType="text/html,text/xml,application/javascript,text/json,text/plain,application/json" />
Select Product
Cumulative Update 9 (CU9)
Fixed issues
Cumulative Update 8 (CU8)
Cumulative Update 7 (CU7)
Cumulative Update 6 (CU6)
Cumulative Update 5 (CU5)
Cumulative Update 4 (CU4)
Cumulative Update 3 (CU3)
Cumulative Update 2 (CU2)
Cumulative Update 1 (CU1)
7.15 LTSR (initial release)
Known issues
Third party notices
Deprecation
Section 508 Voluntary Product Accessibility Template
System requirements
Technical overview
Active Directory
Delivery methods
XenApp published apps and desktops
VM hosted apps
Network ports
Adaptive transport
Double-hop sessions
Install and configure
Prepare to install
Microsoft Azure Resource Manager virtualization environments
Microsoft System Center Virtual Machine Manager virtualization environments
Microsoft System Center Configuration Manager environments
VMware virtualization environments
Nutanix virtualization environments
Microsoft Azure virtualization environments
Install core components
Install VDAs
Install using the command line
Install VDAs using scripts
Install VDAs using SCCM
Create a Site
Create machine catalogs
Manage machine catalogs
Create Delivery Groups
Manage Delivery Groups
Create Application Groups
Manage Application Groups
Remote PC Access
Publish content
Personal vDisk
Install and upgrade
Configure and manage
Displays, messages, and troubleshooting
Remove components
Upgrade and migrate
Changes in 7.x
Upgrade a deployment
Upgrade a XenApp 6.5 worker to a new VDA
Migrate XenApp 6.x
Security considerations and best practices
Integrate XenApp and XenDesktop with NetScaler Gateway
Delegated Administration
Smart cards
Smart card deployments
Pass-through authentication and single sign-on with smart cards
Transport Layer Security (TLS)
Federated Authentication Service
Federated Authentication Service architectures overview
Federated Authentication System how-to - configuration and management
GPU acceleration for Windows Server OS
GPU acceleration for Windows Desktop OS
OpenGL Software Accelerator
Audio features
Browser content redirection
Flash redirection
HTML5 multimedia redirection
Windows Media redirection
General content redirection
Client folder redirection
Host to client redirection
Bidirectional content redirection
Local App Access and URL redirection
USB and client drive considerations
Printing configuration example
Best practices, security considerations, and default operations
Printing policies and preferences
Provision printers
Maintain the printing environment
Work with policies
Policy templates
Create policies
Compare, prioritize, model, and troubleshoot policies
Default policy settings
Policy settings reference
ICA policy settings
Load management policy settings
Profile management policy settings
Receiver policy settings
Virtual Delivery Agent policy settings
Virtual IP policy settings
Configure COM Port and LPT Port Redirection settings using the registry
Connector for Configuration Manager 2012 policy settings
Multi-type licensing
Applications
Universal Windows Platform Apps
Connections and resources
Local Host Cache
Manage security keys
Connection leasing
Virtual IP and virtual loopback
Delivery Controllers
VDA registration
Use Search in Studio
IPv4/IPv6 support
User profiles
Citrix Insight Services
Citrix Scout
Session Recording
Get started with Session Recording
Install, upgrade, and uninstall Session Recording
Configure Session Recording
Grant access rights to users
Create and activate recording policies
Create notification messages
Disable or enable recording
Enable or disable live session playback and playback protection
Enable and disable digital signing
Specify where recordings are stored
Specify file size for recordings
Log administration activities
Install Session Recording with database high availability
View recordings
Troubleshoot Session Recording
Manage your database records
Configuration Logging
Advanced configuration
Monitor deployments
Alerts and notifications
Delegated Administration and Director
Secure Director deployment
Configure permissions for VDAs earlier than XenDesktop 7
Configure network analysis
Troubleshoot user issues
Send messages to users
Restore sessions
Reset a Personal vDisk
Run HDX channel system reports
Shadow users
Diagnose user logon issues
Record sessions
Restore desktop connections
Resolve application failures
Reset a user profile
Troubleshoot applications
Troubleshoot machines
Feature compatibility matrix
Data granularity and retention
Troubleshoot Director failure reasons
SDKs and APIs
Document History
This content has been machine translated dynamically.
Dieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde. (Haftungsausschluss)
Cet article a été traduit automatiquement de manière dynamique. (Clause de non responsabilité)
Este artículo lo ha traducido una máquina de forma dinámica. (Aviso legal)
此内容已经过机器动态翻译。 放弃
このコンテンツは動的に機械翻訳されています。 免責事項
이 콘텐츠는 동적으로 기계 번역되었습니다. 책임 부인
Este texto foi traduzido automaticamente. (Aviso legal)
Questo contenuto è stato tradotto dinamicamente con traduzione automatica. (Esclusione di responsabilità))
This article has been machine translated.
Dieser Artikel wurde maschinell übersetzt. (Haftungsausschluss)
Ce article a été traduit automatiquement. (Clause de non responsabilité)
Este artículo ha sido traducido automáticamente. (Aviso legal)
この記事は機械翻訳されています. 免責事項
이 기사는 기계 번역되었습니다. 책임 부인
Este artigo foi traduzido automaticamente. (Aviso legal)
这篇文章已经过机器翻译. 放弃
Questo articolo è stato tradotto automaticamente. (Esclusione di responsabilità))
Translation failed!
The following table lists the default network ports used by XenApp and XenDesktop Delivery Controllers, Windows VDAs, Director, and Citrix License Server. When Citrix components are installed, the operating system’s host firewall is also updated, by default, to match these default network ports.
For an overview of communication ports used in other Citrix technologies and components, see Communication Ports Used by Citrix Technologies .
You may need this port information:
- For regulatory compliance purposes.
- If there is a network firewall between these components and other Citrix products or components, so you can configure that firewall appropriately.
- If you use a third-party host firewall, such as one provided with an anti-malware package, rather than the operating system’s host firewall.
- If you alter the configuration of the host firewall on these components (usually Windows Firewall Service).
- If you reconfigure any features of these components to use a different port or port range, and then want to disable or block ports that are not used in your configuration. Refer to the documentation for the component for details.
For port information about other components such as StoreFront and Provisioning Services, see the component’s current “System requirements” article.
The table lists only incoming ports; outgoing ports are usually determined by the operating system and use unrelated numbers. Information for outgoing ports is not normally needed for the purposes listed above.
Some of these ports are registered with the Internet Assigned Numbers Authority (IANA). Details about these assignments are available at https://www.iana.org/assignments/port-numbers ; however, the descriptive information held by IANA does not always reflect today’s usage.
Additionally, the operating system on the VDA and Delivery Controller will require incoming ports for its own use. See the Microsoft Windows documentation for details.
- VDA, Delivery Controller, and Director
- Citrix Licensing
The following ports are used for Citrix Licensing.
In this article
This Preview product documentation is Citrix Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Citrix Beta/Tech Preview Agreement.
The development, release and timing of any features or functionality described in the Preview documentation remains at our sole discretion and are subject to change without notice or consultation.
The documentation is for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code or functionality and should not be relied upon in making Citrix product purchase decisions.
If you do not agree, select Do Not Agree to exit.
IMAGES
VIDEO
COMMENTS
Port: 8082 Description: UDP port opened by SuperAgents to forward messages from the McAfee ePO server/Agent Handler. Traffic Direction: Outbound connection from the SuperAgents. Source: https://docs.trellix.com/es/bundle/policy-auditor-6.3.-installation-guide-epolicy-orchestrator/page/GUID-5CB08C20-27C7-48DC-9807-EB19112C0401.html Related Links:
Port Number. Protocol. Where Used. Description. 17. TCP. controller. This is use for certain types of VPN clients that accept a banner (QOTD). During normal operation, this port will only accept a connection and immediately close it. ... 8082. TCP. controller. Used internally for single sign-on authentication (HTTP). Not exposed to wireless ...
Port 8082 not available Ask Question Asked 9 years, 7 months ago Modified 9 years, 6 months ago Viewed 4k times 0 I installed a Jenkins server on port 8080. Then I installed GitBlit, which usually takes port 8080 too, so that I changed to port 8082. On the machine I can call localhost:8082, but from remote 192.168.178.3:8082 is not available.
This exception usually occurs when there is no service listening on the port you are trying to connect to. A couple of things could be happening: You have not started your server. Your server is not waiting to accept connections. You are trying to connect to the wrong port number. Share Follow answered Jun 17, 2015 at 8:54 Arpit Aggarwal
Port numbers are assigned in various ways, based on three ranges: System Ports (0-1023), User Ports (1024-49151), and the Dynamic and/or Private Ports (49152-65535); the different uses of these ranges are described in [ RFC6335 ].
By default, the HTTP port that's used for client-to-site system communication is port 80, and 443 for HTTPS. You can change these ports during setup or in the site properties. Non-configurable ports Configuration Manager doesn't allow you to configure ports for the following types of communication: Site to site Site server to site system
TCP port 8082 uses the Transmission Control Protocol. TCP is one of the main protocols in TCP/IP networks. TCP is a connection-oriented protocol, it requires handshaking to set up end-to-end communications. Only when a connection is set up user's data can be sent bi-directionally over the connection. Attention!
TCP Port 8082 may use a defined protocol to communicate depending on the application. A protocol is a set of formalized rules that explains how data is communicated over a network. Think of it as the language spoken between computers to help them communicate more efficiently.
This uses HTTP port 8059 or 80 by default. To determine this port number, go to the ..\PCCSRV\ofcscan.ini file and check the "Master_DomainPort" parameter. Secure Sockets Layer (SSL) port. This uses port 4343 or 443 by default. When SSL is enabled, this port is used when opening the web console or when installing clients via Web Install.
The Connector Appliance requires an outbound connection to the Active Directory domain via the following ports: Cloud Connector All connections are established from the Cloud Connector to the cloud using the standard HTTPS port (443) and the TCP protocol. No incoming connections are accepted.
Service names and port numbers are used to distinguish between different services that run over transport protocols such as TCP, UDP, DCCP, and SCTP. Service names are assigned on a first-come, first-served process, as documented in [ RFC6335 ]. Port numbers are assigned in various ways, based on three ranges: System Ports (0-1023), User Ports ...
In version 7.x the web UI is accessible via port 8082 and Artifactory's service is still using port 8081. In this example, we will change the port from 8081 to 8080. ... In order to change Artifactory's port number to 8080 it would be required to change the line:<Connector port="8081" sendReasonPhrase="true" relaxedPathChars ...
You can run the following commands to check if the port 8082 is already in use: netstat -ban|find ":8082". netstat -ban|find ":8059". To assign a new port for Smart Scan Server: Stop the Trend Micro Security Server Master Service. Modify the following files by changing the default port 8082 to a new port. Always back up the files and registry ...
On the OSGeoLive VM there are two tomcat containers running one on port 8080 and the other (with GeoServer) on 8082. Apache httpd is running on port 80 to server static web pages and cgi based programs like MapServer.
HTTP/HTTPS Port Number Reference. HTTP and HTTPS ports, default assignments, and protocols. Table 3: Default HTTP/HTTPS Ports; Type Default Protocol Where Configured; Client communications, unsecured. 8080. HTTP. In Management Cockpit ... 8082 (secure) HTTPS. In Management Cockpit, ...
November 5, 2020. Contributed by: C. The following table lists the default network ports used by XenApp and XenDesktop Delivery Controllers, Windows VDAs, Director, and Citrix License Server. When Citrix components are installed, the operating system's host firewall is also updated, by default, to match these default network ports.