[DiscordArchive] Hey I have a question about SOAP support, not sure if this is the right channel.
[DiscordArchive] Hey I have a question about SOAP support, not sure if this is the right channel.
Original source
Hey I have a question about SOAP support, not sure if this is the right channel.
I've got my config setup as follows:
```
SOAP.Enabled = 1
SOAP.IP = "127.0.0.1"
SOAP.Port = 7878
```
and I can see in Docker Desktop that port is being forwarded `7878:7878`. I had to track down the IP that docker assigned that container, using localhost just gave me a connection refused error.
I determined that docker gave it an IP of `172.18.0.4`
When I POST the following payload to that IP and port `172.18.0.4:7878`
```
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/1999/XMLSchema"
xmlns:ns1="urn:AC">
<SOAP-ENV:Body>
<ns1:executeCommand>
<command>server status</command>
</ns1:executeCommand>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
```
I'm always getting request timed out errors. Can anyone point me in the right direction?
rektbyfaith
05-06-2023, 05:41 AM #1Archived author: KeyboardLicker • Posted: 2023-05-06T05:41:02.149000+00:00
Original source
Hey I have a question about SOAP support, not sure if this is the right channel.
I've got my config setup as follows:
```
SOAP.Enabled = 1
SOAP.IP = "127.0.0.1"
SOAP.Port = 7878
```
and I can see in Docker Desktop that port is being forwarded `7878:7878`. I had to track down the IP that docker assigned that container, using localhost just gave me a connection refused error.
I determined that docker gave it an IP of `172.18.0.4`
When I POST the following payload to that IP and port `172.18.0.4:7878`
```
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/1999/XMLSchema"
xmlns:ns1="urn:AC">
<SOAP-ENV:Body>
<ns1:executeCommand>
<command>server status</command>
</ns1:executeCommand>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
```
I'm always getting request timed out errors. Can anyone point me in the right direction?
Original source
hello,dear,I found that after the recent upgrade, multiple clients will be dropped at the same time, who knows why? thanks.
rektbyfaith
05-06-2023, 06:29 AM #2Archived author: GrewRabbit • Posted: 2023-05-06T06:29:35.220000+00:00
Original source
hello,dear,I found that after the recent upgrade, multiple clients will be dropped at the same time, who knows why? thanks.
Original source
I left a project because the license was everyone else had to post code publicly if you were using the software.. which normally wouldn't bother me except they didn't allow pull requests and made you use some private repro so it looked like they were doing all the fixes.. and anything they did (The original authors) didn't have to be publicly posted. Really strange license so I dipped.
rektbyfaith
05-06-2023, 07:13 AM #3Archived author: XSNomad • Posted: 2023-05-06T07:13:07.548000+00:00
Original source
I left a project because the license was everyone else had to post code publicly if you were using the software.. which normally wouldn't bother me except they didn't allow pull requests and made you use some private repro so it looked like they were doing all the fixes.. and anything they did (The original authors) didn't have to be publicly posted. Really strange license so I dipped.
Original source
if you were using fresh azerothcore its because there was a merge where the xp hook was updated
rektbyfaith
05-06-2023, 08:42 AM #4Archived author: Anchy • Posted: 2023-05-06T08:42:37.293000+00:00
Original source
if you were using fresh azerothcore its because there was a merge where the xp hook was updated
Original source
try doing it now
rektbyfaith
05-06-2023, 08:42 AM #5Archived author: Anchy • Posted: 2023-05-06T08:42:40.094000+00:00
Original source
try doing it now
Original source
autobalance has been updated
rektbyfaith
05-06-2023, 08:42 AM #6Archived author: Anchy • Posted: 2023-05-06T08:42:43.070000+00:00
Original source
autobalance has been updated
Original source
ok thanks a lot!
rektbyfaith
05-06-2023, 08:43 AM #7Archived author: Voidnt • Posted: 2023-05-06T08:43:09.215000+00:00
Original source
ok thanks a lot!
Original source
you will need to update autobalance though
rektbyfaith
05-06-2023, 08:43 AM #8Archived author: Anchy • Posted: 2023-05-06T08:43:19.882000+00:00
Original source
you will need to update autobalance though
Original source
np will do
rektbyfaith
05-06-2023, 08:43 AM #9Archived author: Voidnt • Posted: 2023-05-06T08:43:31.743000+00:00
Original source
np will do
Original source
I'm trying to update the server to the new squashed version, while following the little guide from the announcement, but I'm getting this error:
```git checkout df77b5f4f79dfee4dee4f01e7258e1b4e7c1b7e2
fatal: reference is not a tree: df77b5f4f79dfee4dee4f01e7258e1b4e7c1b7e2```
rektbyfaith
05-06-2023, 09:23 AM #10Archived author: vnl • Posted: 2023-05-06T09:23:41.192000+00:00
Original source
I'm trying to update the server to the new squashed version, while following the little guide from the announcement, but I'm getting this error:
```git checkout df77b5f4f79dfee4dee4f01e7258e1b4e7c1b7e2
fatal: reference is not a tree: df77b5f4f79dfee4dee4f01e7258e1b4e7c1b7e2```
1 Guest(s)
1 Guest(s)