[SOLVED] Standard emoticons not rendered
I have a fresh Confluence 6.3 install (official Docker image) and when I edit a page and want to insert new emoticons, I can't see any pictograms/images. Tried it with three browsers - the images are always missing.
Screenshots:
Thanks!
UPDATE:
The isssue is solved now. User error :/
Since I am using Docker, I have created a docker-compose.yaml file. The relevant part looks like this:
version: '2'
services:
confluence:
image: atlassian/confluence-server:6.3
restart: always
ports:
- "127.0.0.1:8090:8090"
depends_on:
- postgres
volumes:
- confluence-data:/var/atlassian/application-data/confluence
- /opt/docker/mount/confluence-cfg-mount/server.xml:/opt/atlassian/confluence/conf/server.xml
- /opt/docker/mount/confluence-cfg-mount/server.xml:/opt/atlassian/confluence/conf/web.xml
As you can see the last line mounts the *contents* of server.xml into the web.xml file. Confluence rightly complains about a directive missing - well the entire web.xml was missing but ok:
23-Aug-2017 16:14:52.643 SEVERE [localhost-startStop-1]org.springframework.web.servlet.DispatcherServlet.initServletBean Context initialization failed
confluence_1 | org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'defaultServletHandlerMapping' defined in class org.springframework.web.servlet.config.annotation.DelegatingWebMvcConfiguration: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.springframework.web.servlet.HandlerMapping]: Factory method 'defaultServletHandlerMapping' threw exception; nested exception is java.lang.IllegalStateException: Unable to locate the default servlet for serving static content. Please set the 'defaultServletName' property explicitly.
The weird thing though is that I did edit the web.xml file before because I changed the session timeout. I don't understand how Confluence was able to change my session timeout even though the web.xml file had the wrong contents...
However, if anybody else stumbles over this - you're welcome. Thank you all for your help. Special thanks to Ann for her dedication and perseverence :)
1 answer
1 accepted
what happens, if you just type (/) on your confluence page?
It should change immediately to:
It doesn't - that's why I have the slight suspicion that something is broken :)
Right after typing it the following happens:
in Chrome:
in Safari:
Started a search re-index but it didn't help.
I tried to access a direct image url:
But then I get a Java Nullpointer exception:
As I mentioned, this is a fairly straightforward setup with the default Docker image. I did import some space, but this problem existed even before importing stuff.
Here is my nginx proxy conf:
user nginx;
worker_processes 1;
#error_log /dev/null;
error_log /var/log/nginx/error.log warn;
pid /var/run/nginx.pid;
events {
worker_connections 1024;
}
http {
include /etc/nginx/mime.types;
default_type application/octet-stream;
log_format main '$remote_addr - $remote_user [$time_local] "$request" '
'$status $body_bytes_sent "$http_referer" '
'"$http_user_agent" "$http_x_forwarded_for" "$proxy_host"';
access_log /dev/null;
#access_log /var/log/nginx/access.log main;
#sendfile on;
#tcp_nopush on;
keepalive_timeout 600;
proxy_connect_timeout 600;
proxy_send_timeout 600;
proxy_read_timeout 600;
gzip on;
include /etc/nginx/conf.d/*.conf;
server {
listen 80 default_server;
server_name myserver;
location /cf {
proxy_set_header X-Forwarded-Host $host:$server_port;
proxy_set_header X-Forwarded-Server $host;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_pass http://confluence:8090/cf;
client_max_body_size 500M;
}
location / {
proxy_set_header X-Forwarded-Port $server_port;
proxy_set_header X-Forwarded-Proto $http_x_forwarded_proto;
proxy_set_header Host $http_host;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_pass http://pihole;
}
}
}
I compared your url with an url from my system's thumbs_up.png
What happens, if you remove the "cf" part from the URL?
But anyway, I think, you have to contact Atlassian Support with this problem.
They can take a deeper look into the problem. You can then refer to this ticket, so you don't have to explain it all again.
Sorry, I couldn't help, good luck :-)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.